| 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 17:50:07 |
| Message-ID: | 4A92D2CF.2030806@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>
>> I don't see why we couldn't move the hba call specifically, though.
>> That's a fairly common error, so it would be good if the output went
>> to the place that is actually configured in postgresql.conf. It's at
>> least a lot more likely than most other things that are prior to
>> syslogger startup.
>>
>
> 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.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Mason | 2009-08-24 17:52:11 | Re: DELETE syntax on JOINS |
| Previous Message | Josh Berkus | 2009-08-24 17:48:37 | Re: 8.5 release timetable, again |