Wed Nov 13 13:48:42 PST 2013
- Previous message: [Slony1-bugs] [Bug 324] New: slony 2.1.4 slon creating extremely long query
- Next message: [Slony1-bugs] [Bug 324] slony 2.1.4 slon creating extremely long query
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=324 --- Comment #1 from Jan Wieck <janwieck at yahoo.com> 2013-11-13 13:48:43 PST --- I do see the order by clause on the log_actionseq select in the REL_2_1_STABLE branch, but the log snippet you pasted clearly shows those numbers out of order. Can you try to reindex the sl_log_* tables? Note that in 2.2 the problem is gone entirely because we no longer use the log_actionseq for that. Instead the log selection for the first SYNC after subscribe is based on the snapshot of the copy_set() operation. At the time we did not feel comfortable to backpatch that into 2.1. That might be a reasonable thing to do now. -- 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 324] New: slony 2.1.4 slon creating extremely long query
- Next message: [Slony1-bugs] [Bug 324] slony 2.1.4 slon creating extremely long query
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list