Re: Postgresql create a core while trying log a message to syslog

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Demarest, Jamie" <Jamie(dot)Demarest(at)saabsensis(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, "Tamayo, Cristofer" <Cristofer(dot)Tamayo(at)saabsensis(dot)com>, "Cornman, Melody" <Melody(dot)Cornman(at)saabsensis(dot)com>
Subject: Re: Postgresql create a core while trying log a message to syslog
Date: 2020-03-11 22:39:58
Message-ID: 5730.1583966398@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Demarest, Jamie" <Jamie(dot)Demarest(at)saabsensis(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kurt Roeckx 2020-03-12 08:58:05 Streaming replication doesn't restart after timeout
Previous Message Alvaro Herrera 2020-03-11 22:14:57 Re: Postgresql create a core while trying log a message to syslog