Stephen Frost [EMAIL PROTECTED] 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
Alvaro Herrera [EMAIL PROTECTED] writes:
On Fri, Feb 04, 2005 at 03:16:33PM -0500, Tom Lane wrote:
Michael Klatt reported here:
http://archives.postgresql.org/pgsql-admin/2005-02/msg00031.php
that we have problems because the flat files global/pg_pwd
and global/pg_group aren't rebuilt
Stephen Frost [EMAIL PROTECTED] writes:
We can't build the files very easily during WAL recovery, but
what about if we compare the files to the database after the normal
backend startup? If they're different, regenerate the files.
This assumes that you can get in in the first place, which is
* Tom Lane ([EMAIL PROTECTED]) wrote:
What I am thinking is that we have to punt on this problem until the
proposed pg_role catalog is in place. With the grolist array
representation of group membership replaced by a fixed-width
pg_role_members catalog, there would be no need to deal with any
* Tom Lane ([EMAIL PROTECTED]) wrote:
Stephen Frost [EMAIL PROTECTED] writes:
We can't build the files very easily during WAL recovery, but
what about if we compare the files to the database after the normal
backend startup? If they're different, regenerate the files.
This assumes that
Sorry, hit the wrong key.
- Forwarded message from Alvaro Herrera [EMAIL PROTECTED] -
Date: Fri, 4 Feb 2005 22:39:11 -0300
From: Alvaro Herrera [EMAIL PROTECTED]
To: Tom Lane [EMAIL PROTECTED]
Subject: Re: [HACKERS] Fixing flat user/group files at database startup
On Fri, Feb 04, 2005
