From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Eric Cyr <eric(dot)cyr(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: SIGTTIN / SIGTTOU handling (was Re: BUG #15449) |
Date: | 2018-11-17 18:35:00 |
Message-ID: | 20181117183500.uiswm6r2p6aw7uux@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
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?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-11-17 19:11:24 | Re: SIGTTIN / SIGTTOU handling (was Re: BUG #15449) |
Previous Message | Tom Lane | 2018-11-17 17:56:32 | SIGTTIN / SIGTTOU handling (was Re: BUG #15449) |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-11-17 19:11:24 | Re: SIGTTIN / SIGTTOU handling (was Re: BUG #15449) |
Previous Message | Tom Lane | 2018-11-17 17:56:32 | SIGTTIN / SIGTTOU handling (was Re: BUG #15449) |