Fri Apr 12 04:04:03 PDT 2013
- Previous message: [Slony1-bugs] [Bug 288] Error occurred when creating new slony-i cluster
- Next message: [Slony1-bugs] [Bug 289] Invalid txid_snapshot in sl_event
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=289 Summary: Invalid txid_snapshot in sl_event Product: Slony-I Version: 2.0 Platform: PC OS/Version: Linux Status: NEW Severity: critical Priority: low Component: slon AssignedTo: slony1-bugs at lists.slony.info ReportedBy: tkarlik at gmail.com CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 Hi, Every so often in table sl_event appears invalid ev_snapshot value. Some txid doubles (like 379383437 below), and postgres complains about invalid input for txid_snapshot type: select * from "pg_catalog".txid_snapshot_xip('379383396:379383451:379383396,379383437,379383437,379383442') ) order by log_actionseq" PGRES_FATAL_ERROR ERROR: invalid input for txid_snapshot: "379383396:379383451:379383396,379383437,379383437,379383442" LINE 1: ...d "pg_catalog".txid_visible_in_snapshot(log_txid, '379383396... The only way to get rid of replication lag is to update sl_event table. For example replacing "379383396:379383451:379383396,379383437,379383437,379383442" with "379383396:379383451:379383396,379383437,379383442" solves the problem. Best regards -- 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 288] Error occurred when creating new slony-i cluster
- Next message: [Slony1-bugs] [Bug 289] Invalid txid_snapshot in sl_event
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list