From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Steben <mark.steben@drivedominion.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: sysout error log being truncated
Date: Fri, 08 Mar 2019 18:09:37 -0500
Message-ID: <22234.1552086577@sss.pgh.pa.us> (raw)
In-Reply-To: <CADyzmyyftHOPk_Tc0MpdYqGKCZ2KeVaqv3rRci5NRYH-+7CTWA@mail.gmail.com>
References: <CADyzmyyftHOPk_Tc0MpdYqGKCZ2KeVaqv3rRci5NRYH-+7CTWA@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, mark.steben@drivedominion.com
Subject: Re: sysout error log being truncated
In-Reply-To: <22234.1552086577@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox