Re: Parsing of pg_hba.conf and authentication inconsistencies

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parsing of pg_hba.conf and authentication inconsistencies
Date: 2008-08-05 14:35:36
Message-ID: 5381.1217946936@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Tom Lane wrote:
>> A point that I don't think has been made so far in the thread: the
>> only place the postmaster could complain in event of problems is the
>> postmaster log, which we know too well isn't watched by inexperienced
>> DBAs. I guarantee you that we will get bug reports along the lines of
>> "I updated pg_hba.conf and did pg_ctl reload, but nothing changed!
>> Postgres sucks!" if we implement checking at load time.

> How is this different from how we deal with postgresql.conf today?

It isn't, and I seem to recall we've had that scenario play out a couple
times already for postgresql.conf changes. But pg_hba.conf is far more
complex than "variable = value" ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2008-08-05 14:44:14 Re: Parsing of pg_hba.conf and authentication inconsistencies
Previous Message Robert Treat 2008-08-05 14:33:15 Re: CommitFest July Over