Tue Jan 10 02:03:01 PST 2012
- Previous message: [Slony1-bugs] [Bug 256] set_config_option has parm change in HEAD
- Next message: [Slony1-bugs] [Bug 259] It is an error in the cluster that runs the TRUNCATE using uppercase CLUSTER_NAME
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=259 Summary: It is an error in the cluster that runs the TRUNCATE using uppercase CLUSTER_NAME Product: Slony-I Version: 2.0 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: low Component: slonik AssignedTo: slony1-bugs at lists.slony.info ReportedBy: mfgoogle at yahoo.co.jp CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 It is an error in the cluster that runs the TRUNCATE using uppercase CLUSTER_NAME. [My environment] Vine Linux: 4.2 Kernel: 2.6.16-76.55vl4 #1 SMP PostgreSQL: 9.0.4 slony-I: 2.1.0 CPU: Intel(R) Pentium(R) D CPU 2.80GHz MailMemory: 2GB [summary] My configuration file for slon_tools(altperl):: --- cut ... $CLUSTER_NAME = 'MAIL'; ... --- cut execution log:: --- cut maildb=# TRUNCATE tablename ; ERROR: schema "_mail" does not exist line 2: ...node, pg_catalog.txid_current(), c_tabid, nextval('_MAIL.. ^ QUERY: insert into "_MAIL".sl_log_1 (log_origin, log_txid, log_tableid, log_actionseq, log_cmdtype, log_cmddata) values (c_node, pg_catalog.txid_current(), c_tabid, nextval('_MAIL.sl_action_seq'), 'T', c_command) CONTEXT: PL/pgSQL function "log_truncate" line 14 at SQL statement --- cut -- 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. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 256] set_config_option has parm change in HEAD
- Next message: [Slony1-bugs] [Bug 259] It is an error in the cluster that runs the TRUNCATE using uppercase CLUSTER_NAME
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list