From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Thoughts on the location of configuration files |
Date: | 2001-12-24 03:43:59 |
Message-ID: | 6391.1009165439@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Well, the problem with backward compatibility here is that now we have
> pg_hba.conf to configure some part of local authentication and
> postgresql.conf to configure the other part.
Seems a pretty empty argument. pg_ident.conf also (now) bears on local
authentication, as does any random secondary-password file the user
might select. Shall we find a way to smush all that into pg_hba.conf?
> Aren't the socket permissions best dealt with in pg_hba.conf?
Maybe if we were designing the whole thing from scratch, it'd be cleaner
to do it that way ... but it doesn't seem enough cleaner to justify
creating a compatibility issue.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-12-24 03:49:38 | Re: Thoughts on the location of configuration files |
Previous Message | Bruce Momjian | 2001-12-24 03:35:58 | Re: Thoughts on the location of configuration files |