| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, 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-12 18:55:53 |
| Message-ID: | CA+TgmoZgxb+GTaw7JgNr1QariC8GNWHaB=Qx3b-wcQOfXDspfw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 11, 2018 at 7:09 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> I think the new behavior where the GUC only takes effect at next checkpoint
> is OK. It seems quite intuitive.
I think it may actually be confusing. If you run pg_ctl reload and it
reports that the value has changed, you'll expect it to have taken
effect. But really, it will take effect at some later time.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-04-12 19:05:37 | Re: Native partitioning tablespace inheritance |
| Previous Message | Robert Haas | 2018-04-12 18:49:42 | Re: Instability in the postgres_fdw regression test |