From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [WIP] Add relminxid column to pg_class |
Date: | 2006-04-10 03:57:11 |
Message-ID: | 20060410035711.GA28647@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Tom Lane wrote:
> I see a workaround though: it *is* OK for VACUUM FREEZE to set datminxid
> = FrozenXid if (1) it's been able to freeze all the tables and (2) it's
> running in a standalone backend. This rule would let us freeze
> template0 during initdb.
>
> There's still a question of where/when to worry about marking a database
> unfrozen. Perhaps a suitably cheap, conservative approximation would be
> to cause any new connection to a frozen database to immediately mark it
> unfrozen in pg_database. (I'm not sure if this works conveniently for
> initdb's processing though --- we might want to fudge a bit depending on
> whether we're running standalone.)
initdb never connects to template0, so I think it should work. We just
need to add an additional step to initdb to run the vacuum freeze.
What do you think of making vacuum a no-op on a table that has datminxid
= FrozenXid?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-04-10 04:04:58 | Re: [WIP] Add relminxid column to pg_class |
Previous Message | Tom Lane | 2006-04-10 02:26:12 | Re: [WIP] Add relminxid column to pg_class |