From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Robert Fitzpatrick <robert(at)webtent(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Changes to pg_hba.conf not effective until after restart |
Date: | 2002-12-23 15:59:37 |
Message-ID: | 200212231559.gBNFxbt10135@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Robert Fitzpatrick wrote:
> Can anyone tell me why on one of our PostgreSQL servers, anytime a
> change is made to the pg_hba.conf file, the PostgreSQL must be restarted
> before the changes take affect? We have other older versions of
> PostgreSQL that changes are effective immediately without restart. Is
> there some setting for this?
It was considered a safety change, so it doesn't read the file as you
are modifying it.
The 7.2 release notes state:
* The "pg_hba.conf" and "pg_ident.conf" configuration is now only
reloaded after receiving a SIGHUP signal, not with each
connection.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Choe | 2002-12-23 16:04:33 | Re: encryption function |
Previous Message | Bruce Momjian | 2002-12-23 15:58:40 | Re: encryption function |