Re: Problem while setting the fpw with SIGHUP

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Problem while setting the fpw with SIGHUP
Дата
Msg-id CA+TgmoZgxb+GTaw7JgNr1QariC8GNWHaB=Qx3b-wcQOfXDspfw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Problem while setting the fpw with SIGHUP  (Heikki Linnakangas <hlinnaka@iki.fi>)
Ответы Re: Problem while setting the fpw with SIGHUP  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
On Wed, Apr 11, 2018 at 7:09 AM, Heikki Linnakangas <hlinnaka@iki.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Instability in the postgres_fdw regression test
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Native partitioning tablespace inheritance