From: Noah Misch <noah@leadboat.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Consistently test for in-use shared memory.
Date: Mon, 15 Apr 2019 17:50:19 -0700
Message-ID: <20190416005019.GA3296237@rfd.leadboat.com> (raw)
In-Reply-To: <26478.1555373328@sss.pgh.pa.us>
References: <E1hFBbx-0002OI-Pb@gemulon.postgresql.org>
<26478.1555373328@sss.pgh.pa.us>
On Mon, Apr 15, 2019 at 08:08:48PM -0400, Tom Lane wrote:
> Noah Misch <noah@leadboat.com> writes:
> > Consistently test for in-use shared memory.
>
> Hmm ... conchuela has just found another problem with this test case:
>
> ok 2 - detected live backend via shared memory
> # Running: postgres --single -D /home/pgbf/buildroot/HEAD/pgsql.build/src/test/recovery/tmp_check/t_017_shm_gnat_data/pgdata template1
> ack Broken pipe: write( 16, 'SELECT 1 + 1' ) at /usr/local/lib/perl5/site_perl/IPC/Run/IO.pm line 549.
>
> I interpret this as "the single-user backend exited before we could stuff
> 'SELECT 1 + 1' down the pipe to it, and the Perl script is not expecting
> to get a write failure there".
Perhaps I should write the 'SELECT 1 + 1' to a regular file and redirect input
from that file.
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-committers@postgresql.org
Cc: noah@leadboat.com, tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Consistently test for in-use shared memory.
In-Reply-To: <20190416005019.GA3296237@rfd.leadboat.com>
* 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