Tue Dec 8 13:00:24 PST 2009
- Previous message: [Slony1-commit] slony1-engine/src/backend slony1_funcs.sql
- Next message: [Slony1-commit] slony1-engine/src/ducttape test_1_pgbench.in test_1_update_functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine/src/backend
In directory main.slony.info:/tmp/cvs-serv5338
Modified Files:
Tag: REL_1_2_STABLE
slony1_funcs.sql
Log Message:
drop_if_exist() used '@NAMESPACE@' too check if the function exists,
resulting in '"_CLUSTERNAME"', which of course never exists. Correct
is to look for '_ at CLUSTERNAME@'.
Jan
Index: slony1_funcs.sql
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/src/backend/slony1_funcs.sql,v
retrieving revision 1.98.2.44
retrieving revision 1.98.2.45
diff -C2 -d -r1.98.2.44 -r1.98.2.45
*** slony1_funcs.sql 3 Dec 2009 22:54:40 -0000 1.98.2.44
--- slony1_funcs.sql 8 Dec 2009 21:00:22 -0000 1.98.2.45
***************
*** 3765,3773 ****
v_drop text;
begin
! if exists (select 1 from information_schema.routines where routine_schema = ''@NAMESPACE@'' and routine_name = p_function) then
v_drop := ''drop function @NAMESPACE at .'' || p_function || ''('' || p_args || '');'';
execute v_drop;
end if;
! return 1;
end
' language plpgsql;
--- 3765,3774 ----
v_drop text;
begin
! if exists (select 1 from information_schema.routines where routine_schema = ''_ at CLUSTERNAME@'' and routine_name = p_function) then
v_drop := ''drop function @NAMESPACE at .'' || p_function || ''('' || p_args || '');'';
execute v_drop;
+ return 1;
end if;
! return 0;
end
' language plpgsql;
- Previous message: [Slony1-commit] slony1-engine/src/backend slony1_funcs.sql
- Next message: [Slony1-commit] slony1-engine/src/ducttape test_1_pgbench.in test_1_update_functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list