On Fri, Aug 28, 2009 at 12:12 PM, Tom Lane wrote:
> "Joshua D. Drake" writes:
>> On Fri, 2009-08-28 at 11:52 -0400, Tom Lane wrote:
>>> I've thought of an easier way to handle this: if the given database name
>>> is invalid, connect to database "postgres" instead, and perform
>>> authentication us
"Joshua D. Drake" writes:
> On Fri, 2009-08-28 at 11:52 -0400, Tom Lane wrote:
>> I've thought of an easier way to handle this: if the given database name
>> is invalid, connect to database "postgres" instead, and perform
>> authentication using normal access to the pg_auth catalogs. If
>> authen
On Fri, 2009-08-28 at 11:52 -0400, Tom Lane wrote:
> I've thought of an easier way to handle this: if the given database name
> is invalid, connect to database "postgres" instead, and perform
> authentication using normal access to the pg_auth catalogs. If
> authentication succeeds, *then* throw
I'm back on the warpath about $SUBJECT. (Aside from any other reason to
do it, it occurs to me that we really need to get rid of the flat files
for Hot Standby. Otherwise we'd need some way to keep them up to date
during WAL replay.) I wrote earlier:
> The easy way to do it would be to postpone
I've been looking into what it would take to eliminate the flat file for
pg_auth info. The implication of doing that is that authentication has
to be postponed until inside InitPostgres(), where we can read the
actual system catalogs instead.
The easy way to do it would be to postpone authenticat
