Oh great! After resetting log_min_error_statement =3D notice, doing pg_ctl =
reload & stopping & restarting slon on both master & slave, the problem no =
longer occurs. Isn't that a strange cowinkydink? :)=A0 fyi, I had done mult=
iple restarts of slon prior to this, so it seems strange that just changing=
 log_min_error_statement would resolve.

At any rate, thanks very much for the suggestion and I'll keep monitoring t=
o see if the problem reoccurs.

Melvin Davidson =

 =

Hrm.  Try setting log_min_error_statement =3D notice.  That maybe will
show up the same statements as are in the slony log you have, which
would at least confirm that slony is logging what's really a notice.

A

-- =

Andrew Sullivan
ajs at crankycanuck.ca
_______________________________________________
Slony1-general mailing list
Slony1-general at lists.slony.info
http://lists.slony.info/mailman/listinfo/slony1-general



      =

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20090501/=
302e6caa/attachment.htm