Bruce Momjian <pgman@candle.pha.pa.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
