From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
Cc: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: Eric Cyr <eric.cyr@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: SIGTTIN / SIGTTOU handling (was Re: BUG #15449)
Date: Sat, 17 Nov 2018 14:11:24 -0500
Message-ID: <28166.1542481884@sss.pgh.pa.us> (raw)
In-Reply-To: <20181117183500.uiswm6r2p6aw7uux@alvherre.pgsql>
References: <20181117183500.uiswm6r2p6aw7uux@alvherre.pgsql>
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2018-Nov-17, Tom Lane wrote:
>> Given the lack of complaints, there's probably no need for back-patch,
>> but that's what I'd propose in HEAD to make this saner.
> Hmm, but the bug was reported on pg10 ... why wouldn't we backpatch this
> fix there?
The complaint was about SIGPIPE handling (or lack of it). I do intend
to back-patch the fix for that. This is just a side issue that came
up in that thread.
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, alvherre@2ndquadrant.com, thomas.munro@enterprisedb.com, fujita.etsuro@lab.ntt.co.jp, horiguchi.kyotaro@lab.ntt.co.jp, eric.cyr@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: SIGTTIN / SIGTTOU handling (was Re: BUG #15449)
In-Reply-To: <28166.1542481884@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