My last email was written before reading this. A few episodes of 24 occurred between writing and sending that email.
Added slony1-hackers, but didn't remove pgsql-hackers. Feel free to exclude pgsql lists, as this branch of conversation seems to be more Slony related than Postgres.
On Sun, May 26, 2013 at 10:59 PM, Christopher Browne
<cbbrowne@gmail.com> wrote:
Commit log says it was fixed between 2.1.2, but from the Slony logs at the time, the version in use was 2.1.2. So
Joking about "640K" aside, it doesn't seem reasonable to expect a truly enormous query as is generated by the broken forms of this logic to turn out happily. I'd rather fix Slony (as done in the above patch).
Yes, by all means, fix the application, but that doesn't preclude the argument that the database should be a bit more smarter and efficient, especially if it is easy to do.
Best regards,
--