Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jCA1D-0002dW-M1 for pgsql-bugs@arkaria.postgresql.org; Wed, 11 Mar 2020 22:40:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jCA1C-000339-48 for pgsql-bugs@arkaria.postgresql.org; Wed, 11 Mar 2020 22:40:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jCA1B-00032o-PZ for pgsql-bugs@lists.postgresql.org; Wed, 11 Mar 2020 22:40:01 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jCA19-0007Br-9d for pgsql-bugs@lists.postgresql.org; Wed, 11 Mar 2020 22:40:00 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 02BMdw2g005731; Wed, 11 Mar 2020 18:39:58 -0400 From: Tom Lane To: "Demarest, Jamie" cc: "pgsql-bugs@lists.postgresql.org" , "Tamayo, Cristofer" , "Cornman, Melody" Subject: Re: Postgresql create a core while trying log a message to syslog In-reply-to: <3db74722-18cf-44dd-af9a-2575af201b66@CORPMAIL01.corp.sensis.com> References: <3db74722-18cf-44dd-af9a-2575af201b66@CORPMAIL01.corp.sensis.com> Comments: In-reply-to "Demarest, Jamie" message dated "Wed, 11 Mar 2020 18:24:45 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5729.1583966398.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 11 Mar 2020 18:39:58 -0400 Message-ID: <5730.1583966398@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "Demarest, Jamie" writes: > psql logging has been set up to log to syslog. When the syslog director= y 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