Re: Possible problem with pg_reload_conf() and view pg_settings

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Possible problem with pg_reload_conf() and view pg_settings
Date: 2005-11-05 02:36:44
Message-ID: dkh5r8$2s8$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote in message
news:18807(dot)1131149902(at)sss(dot)pgh(dot)pa(dot)us(dot)(dot)(dot)
> Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> writes:
>> However I was under the impression that if I did a pg_reload_conf(), the
>> pg_settings view would be updated at that time, but that does not seem to
>> happen.

I repeated Tony's result (Win32):

Welcome to psql 8.1RC1, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

test=# select setting from pg_settings where name = 'constraint_exclusion';
setting
---------
off
(1 row)

test=# select pg_reload_conf();
pg_reload_conf
----------------
t
(1 row)

test=# select setting from pg_settings where name = 'constraint_exclusion';
setting
---------
off
(1 row)

test=# LOG: received SIGHUP, reloading configuration files

test=# select setting from pg_settings where name = 'constraint_exclusion';
setting
---------
off
(1 row)

test=# select setting from pg_settings where name = 'constraint_exclusion';
setting
---------
on
(1 row)

-- Seems that's due to delay of process SIGHUP ...

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2005-11-05 02:51:38 Re: Possible problem with pg_reload_conf() and view pg_settings
Previous Message Tom Lane 2005-11-05 01:06:39 Re: Crash during elog.c...