> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> 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?
>
> Both. client_auth.sgml specifically states that editing the file
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> 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?
Both. client_auth.sgml specifically states that editing the file is
sufficient
On Tuesday 31 July 2001 19:20, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > 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
> 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 ... b
