Re: hba load error and silent mode

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: hba load error and silent mode
Date: 2009-08-24 18:51:28
Message-ID: 4A92E130.2040900@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> Tom Lane wrote:
>>
>>> Oh, you mean move load_hba *down*, past the syslogger startup?
>>> Yeah, that would probably be all right.
>>>
>
>
>> Well, that's what I originally said, yes ;-)
>>
>
>
>> But I don't think that precludes your more general suggestion regarding
>> startup errors. In particular, I think moving the hba load down would be
>> reasonable to backpatch to 8.4, whereas I doubt the general fix would.
>>
>
> Well, the change I had in mind is only a few lines of code, and is
> fixing a behavior that you yourself are arguing is unusably broken.
> It seems like a reasonable back-patch candidate to me if we think this
> is a serious bug. But I personally wasn't seeing any of this as due for
> back-patching. The -S behavior has been like it is since forever, and
> nobody's complained before.
>
>
>

We didn't check HBA validity at startup time before, did we? I would not
be surprised to get more complaints now.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2009-08-24 19:09:40 Re: Determining client_encoding from client locale
Previous Message Alvaro Herrera 2009-08-24 18:47:42 Re: SIGUSR1 pingpong between master na autovacum launcher causes crash