Mark Steben <mark.steben@drivedominion.com> writes:
> One of our transactions is a queue processor that generates a ton of insert
> statements per run of this transaction - as many as 1000 per run.
> What has happened in new datacenter is that these transactions - while
> running correctly and completely - do not write all the insert statements
> to our sysout log - only some.
Most, if not all, implementations of syslog will drop messages under
sufficient load; I think they consider that a feature. It's not Postgres'
fault and there's nothing we can do about it. Use a different logging
mechanism if you can't afford to lose any messages.
regards, tom lane
