> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> Would it make sense to do fstat calls on these files and reload whenever
> >> we observe that the file modification time has changed? That'd be an
> >> additional kernel call per connection attempt, so I'm not at all sure
> >> I want to do it ... but it ought to be debated. Comments anyone?
>
> > We could, but we don't with postgresql.conf so it made sense to keep the
> > behavior the same for the two files.
>
> I'm inclined to agree --- for one thing, this allows one to edit the
> files in place without worrying that the postmaster will pick up a
> partially-edited file. But I wanted to throw the issue out to pghackers
> to see if anyone would be really unhappy about having to SIGHUP the
> postmaster after changing the authorization conf files.
OK.
> In any case, if we don't change the code, the change in behavior from
> prior releases needs to be documented...
You mean in the SGML or in the release highlight text?
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
