Re: Problem while setting the fpw with SIGHUP

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, 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-13 17:06:22
Message-ID: CA+TgmoanLz9qZvtbs=d2JaXD5ox_ShEnCop23FLD7W098ahh_Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 12, 2018 at 9:29 PM, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Still does it matter when the change is effective?

I don't really care deeply about when the change takes effect, but I
do care about whether the time when the system *says* the change took
effect is the same as when it *actually* took effect. If those aren't
the same, it's confusing.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-04-13 17:12:28 Re: [HACKERS] path toward faster partition pruning
Previous Message Robert Haas 2018-04-13 17:04:03 Re: [HACKERS] Runtime Partition Pruning