"Jeff Boes" <[EMAIL PROTECTED]> writes:
>> Did this come about because of the increase in WAL count?
No.
> Oops. This turns out not to be a COMMIT time, but instead it's happening
> in a NOTIFY operation just after the COMMIT. What would cause a
> previously-quick NOTIFY step to become many minutes long?
Have you vacuumed pg_listener recently?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
