Thu Aug 18 08:28:01 PDT 2011
- Previous message: [Slony1-bugs] [Bug 234] New: pg_dump + restore of a slony node leaves the node corrupt
- Next message: [Slony1-bugs] [Bug 235] New: SYNC GROUP size bugs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=234 --- Comment #1 from Steve Singer <ssinger at ca.afilias.info> 2011-08-18 08:28:01 PDT --- If you try to use pg_upgrade with slony you will hit a somewhat similar problem in that pg_upgrade does not bring over the transaction id epoch so the 64 bit transaction id numbers that slony gets after the pg_upgrade might seem earlier than the ones from before. pg_resetxlog has a -e option that allows you to set the transaction id epoch. This *might* solve the problem (when using pg_upgrade). -- 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 234] New: pg_dump + restore of a slony node leaves the node corrupt
- Next message: [Slony1-bugs] [Bug 235] New: SYNC GROUP size bugs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list