Re: pgsql: Consistently test for in-use shared memory.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Consistently test for in-use shared memory.
Date: 2019-04-16 00:52:36
Message-ID: 28362.1555375956@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Noah Misch <noah(at)leadboat(dot)com> writes:
> On Mon, Apr 15, 2019 at 08:08:48PM -0400, Tom Lane wrote:
>> 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.

Yeah, that was the first idea that occurred to me as well.
Kinda grotty, but ...

Another idea is to shove the problem off on a sub-shell, that is run

echo SELECT 1 + 1 | postgres --single ...

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2019-04-16 01:01:45 Re: pgsql: Consistently test for in-use shared memory.
Previous Message Noah Misch 2019-04-16 00:50:19 Re: pgsql: Consistently test for in-use shared memory.