From: Tom Lane <tgl@sss.pgh.pa.us>
To: Demarest, Jamie <Jamie.Demarest@saabsensis.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Cc: Tamayo, Cristofer <Cristofer.Tamayo@saabsensis.com>
Cc: Cornman, Melody <Melody.Cornman@saabsensis.com>
Subject: Re: Postgresql create a core while trying log a message to syslog
Date: Wed, 11 Mar 2020 18:39:58 -0400
Message-ID: <5730.1583966398@sss.pgh.pa.us> (raw)
In-Reply-To: <3db74722-18cf-44dd-af9a-2575af201b66@CORPMAIL01.corp.sensis.com>
References: <3db74722-18cf-44dd-af9a-2575af201b66@CORPMAIL01.corp.sensis.com>
"Demarest, Jamie" <Jamie.Demarest@saabsensis.com> writes:
> psql logging has been set up to log to syslog. When the syslog directory filled up psql trying to log to syslog cause psql to core.
This looks more like a PANIC due to corrupt data than what you're
claiming the cause is. I wonder whether the out-of-disk-space
problem had affected previous attempts to write to WAL.
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, Jamie.Demarest@saabsensis.com, pgsql-bugs@lists.postgresql.org, Cristofer.Tamayo@saabsensis.com, Melody.Cornman@saabsensis.com
Subject: Re: Postgresql create a core while trying log a message to syslog
In-Reply-To: <5730.1583966398@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