Re: Problem while setting the fpw with SIGHUP

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Problem while setting the fpw with SIGHUP
Date: 2018-04-23 23:52:17
Message-ID: 20180423235217.GB1570@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 23, 2018 at 12:21:04PM -0400, Robert Haas wrote:
> Fine, but that doesn't answer the question of whether we actually need
> to or should change the behavior in the first place.

Per the last arguments that would be "No, we don't want to change it as
it would surprise some users":
https://www.postgresql.org/message-id/20180420010402.GF2024@paquier.xyz
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-04-23 23:57:58 Re: perltidy version
Previous Message Michael Paquier 2018-04-23 23:49:28 Re: Make description of heap records more talkative for flags