Re: best method of reloading pg_hba.conf

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Hannu Krosing <hannu(at)tm(dot)ee>, David Ford <david(at)blue-labs(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: best method of reloading pg_hba.conf
Date: 2001-11-10 00:28:41
Message-ID: 29258.1005352121@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> But can't we read it only when needed ?
>> Just stat'ing it should be much cheaper than reading it each time.

We'd already created a precedent for read-on-HUP for postgresql.conf,
and no one seemed to be complaining about that. So although this change
will doubtless annoy some existing users, I don't see a big problem
with it. I'm happy to avoid the stat() call --- every kernel call we
can remove from the startup sequence is another small win.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-11-10 00:32:00 Re: Possible major bug in PlPython (plus some other ideas)
Previous Message Fernando Nasser 2001-11-10 00:21:02 Re: best method of reloading pg_hba.conf