Wed Nov 25 06:40:00 PST 2009
- Previous message: [Slony1-bugs] [Bug 103] insert error in function moveSet_int
- Next message: [Slony1-bugs] [Bug 103] insert error in function moveSet_int
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=103 Cyril Scetbon <cyril.scetbon at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Cyril Scetbon <cyril.scetbon at free.fr> 2009-11-25 06:40:00 --- I've found in postgresql 8.3 sources that xmin and xmax can't equal 0. extract from postgresql-8.3.1-sources/backend/utils/adt/txid.c (in parse_snapshot function definition): /* it should look sane */ if (xmin == 0 || xmax == 0 || xmin > xmax) goto bad_format; This error may be due to the fact that before postgresql 8.3, slony has implemented its proper functions which were certainly different from the new functions. -- 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 103] insert error in function moveSet_int
- Next message: [Slony1-bugs] [Bug 103] insert error in function moveSet_int
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list