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

Поиск
Список
Период
Сортировка
От tgl@svr1.postgresql.org (Tom Lane)
Тема pgsql: When cloning template0 (or other fully-frozen databases), set the
Дата
Msg-id 20050312213355.8D42056614@svr1.postgresql.org
обсуждение исходный текст
Список 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 по дате отправления:

Предыдущее
От: tgl@svr1.postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Fix ALTER DATABASE RENAME to allow the operation if user is a
Следующее
От: momjian@svr1.postgresql.org (Bruce Momjian)
Дата:
Сообщение: pgsql: Document aliases for our supported encodings.