| From: | Fernando Nasser <fnasser(at)redhat(dot)com> |
|---|---|
| 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:21:02 |
| Message-ID: | 3BEC72EE.88155C27@redhat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> > > Performance. Peter E found that considerable startup time was being
> > > wasted reading the file.
> >
> > But can't we read it only when needed ?
> >
> > Just stat'ing it should be much cheaper than reading it each time.
>
> We thought about that but it seems we could be reading partial writes to
> the file. This way the administrator controls when the changes become
> effective.
>
Hannu,
It is not only much safer (you get a 2nd chance to check what you've
done)
but is also consistent with the behavior of other Unix daemons.
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser(at)redhat(dot)com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-11-10 00:28:41 | Re: best method of reloading pg_hba.conf |
| Previous Message | Tom Lane | 2001-11-10 00:16:54 | Re: Bug?? -- Alter table drop constraint doesn't seem to work on a primary key constraint in 7.2beta2 |