From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: When cloning template0 (or other fully-frozen databases), set the |
Date: | 2005-03-12 21:33:55 |
Message-ID: | 20050312213355.8D42056614@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
When cloning template0 (or other fully-frozen databases), set the new
database's datallowconn and datfrozenxid to the current transaction ID
instead of copying the source database's values. This is OK because we
assume the source DB contains no normal transaction IDs whatsoever.
This keeps VACUUM from immediately starting to complain about unvacuumed
databases in the situation where we are more than 2 billion transactions
out from the XID stamp of template0. Per discussion with Milen Radev
(although his complaint turned out to be due to something else, but the
problem is real anyway).
Modified Files:
--------------
pgsql/src/backend/commands:
dbcommands.c (r1.153 -> r1.154)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c.diff?r1=1.153&r2=1.154)
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-03-13 00:34:57 | Re: [COMMITTERS] pgsql: Handle carriage returns and line feeds in |
Previous Message | Tom Lane | 2005-03-12 21:12:18 | pgsql: Fix ALTER DATABASE RENAME to allow the operation if user is a |