Mon Nov 14 10:21:03 PST 2011
- Previous message: [Slony1-bugs] [Bug 235] SYNC GROUP size bugs
- Next message: [Slony1-bugs] [Bug 249] TRUNCATE log trigger not working quite right
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=249 Summary: TRUNCATE log trigger not working quite right Product: Slony-I Version: devel Platform: PC OS/Version: Linux Status: ASSIGNED Severity: enhancement Priority: low Component: stored procedures AssignedTo: cbbrowne at ca.afilias.info ReportedBy: cbbrowne at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 slonyregress1 at localhost-> truncate table5; ERROR: missing FROM-clause entry for table "pg_catalog" LINE 2: values (c_node, pg_catalog.txid_current, c_tabid, ne... ^ QUERY: insert into "_slony_regress1".sl_log_2 (log_origin, log_txid, log_tableid, log_actionseq, log_cmdtype, log_cmddata) values (c_node, pg_catalog.txid_current, c_tabid, nextval('_slony_regress1.sl_action_seq'), 'T', c_command) CONTEXT: PL/pgSQL function "log_truncate" line 17 at SQL statement slonyregress1 at localhost-> The entry for sl_log_2 is missing parentheses for the call to txid_current(). -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
- Previous message: [Slony1-bugs] [Bug 235] SYNC GROUP size bugs
- Next message: [Slony1-bugs] [Bug 249] TRUNCATE log trigger not working quite right
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list