| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mark Steben <mark(dot)steben(at)drivedominion(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: sysout error log being truncated |
| Date: | 2019-03-08 23:09:37 |
| Message-ID: | 22234.1552086577@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Mark Steben <mark(dot)steben(at)drivedominion(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter | 2019-03-09 00:17:07 | Re: Upgrade 10.5->10.6 : db crash BUS ERROR (sig 10), reproducible |
| Previous Message | Mark Steben | 2019-03-08 22:22:16 | sysout error log being truncated |