From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Fixing flat user/group files at database startup |
Date: | 2005-02-06 17:24:58 |
Message-ID: | 4932.1107710698@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> I guess I'm confused by 'who' needs to 'get in' to have a bit of code
> run at the very end of the backend startup. Apparently I'm somewhat
> naive in that area.
The point is that the postmaster is going to use the flat files to
check whether you're allowed to log in in the first place. It does
you little good to have a fixup routine in place in backend startup
if you're not allowed to get that far.
(Indeed, one of the points on my personal TODO list entry for this
problem is to make sure the postmaster doesn't try to use the flat
files before we know they've been brought up to date. Right at the
moment it loads them before even launching the WAL replay process...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Mayer | 2005-02-06 17:29:52 | Re: Query optimizer 8.0.1 (and 8.0) |
Previous Message | Larry Rosenman | 2005-02-06 17:16:38 | Re: Failed assertion on cluster |