Re: Parsing of pg_hba.conf and authentication inconsistencies

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:44:14
Message-ID: 4898673E.3060307@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> 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" ...

Ok, then I didn't misunderstand that part at least :-)

Ah, well. I know that if others don't pipe in on my side of it, I'm
implicitly out-voted ;), since I've stated my case by now... Thus, I
won't put any time into working on it unless someone does.

//Magnus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-08-05 14:51:25 Status of DISTINCT-by-hashing work
Previous Message Tom Lane 2008-08-05 14:35:36 Re: Parsing of pg_hba.conf and authentication inconsistencies