Possibly resolves bug http://www.slony.info/bugzilla/show_bug.cgi?id=264 where log_actionseq values are being generated in random-ish order, which means that subscriptions that take a long, long time tend to have a LOT of log_actionseq values to exclude, which builds into a query so large that it blows out the Postgres query parser.

Imposing by-log_actionseq order should rectify this.

Branch
------
REL_2_1_STABLE

Details
-------
http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=c4ac435308a78a2db63bf267d401d842c169e87d
Author: Christopher Browne <cbbrowne at acm.org>

Modified Files
--------------
src/slon/remote_worker.c |    8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)