pgsql: When cloning template0 (or other fully-frozen databases), set the - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: When cloning template0 (or other fully-frozen databases), set the
Date
Msg-id 20050312213355.8D42056614@svr1.postgresql.org
Whole thread Raw
List 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)

pgsql-committers by date:

Previous
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix ALTER DATABASE RENAME to allow the operation if user is a
Next
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Document aliases for our supported encodings.