From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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-05 20:26:22 |
Message-ID: | 20050205202622.GL10437@ns.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) 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
> potentially-toasted columns while extracting the data needed for the
> flat files.
While that sounds alright to me, I was wondering if it'd be possible to
take a slightly different approach to it so we could solve it for
8.0.x... 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. Maybe I'm
missing something here, but that seems pretty straight-forward to me...
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2005-02-05 20:44:52 | Cross column statistics |
Previous Message | Oliver Jowett | 2005-02-05 19:49:02 | Re: Patch Count? |