http://www.slony.info/bugzilla/show_bug.cgi?id=264

--- Comment #1 from Christopher Browne <cbbrowne at ca.afilias.info> 2012-04-25 13:52:44 PDT ---
It seems as though there has been a change in behaviour...

This was *supposed* to have been fixed by patch
http://git.postgresql.org/gitweb/?p=slony1-engine.git;a=commit;h=43b650085fe7195b6d4b5f97b7b9bb84d92feea1

That patch compresses sequences of adjacent log_actionseq numbers together.

Unfortunately, it appears from the bits of the query that are included that the
values are no longer in any sort of adjacent order.

I don't see any ORDER BY clauses against the queries that seem likely to be
pulling data that goes into ssy_action_list (which is what gets compressed by
compress_actionseq()); I expect that adding ORDER BY 1 would do the trick,
albeit at some non-zero cost to some queries that would now require sorts.

Note that compress_actionseq() takes the representation that you see, and
replaces any runs possible with "... and log_actionseq not between '%d' and
'%d'".  If there are large numbers of consecutive log_actionseq values, then a
LOT of those will get compressed into a few clauses.

-- 
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.