pgsql: WAL must log CREATE and DROP DATABASE operations *without* using

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: WAL must log CREATE and DROP DATABASE operations *without* using
Date: 2005-03-23 00:04:28
Message-ID: 20050323000428.10A1E5678B@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
WAL must log CREATE and DROP DATABASE operations *without* using any
explicit paths, so that the log can be replayed in a data directory
with a different absolute path than the original had. To avoid forcing
initdb in the 8.0 branch, continue to accept the old WAL log record
types; they will never again be generated however, and the code can be
dropped after the next forced initdb. Per report from Oleg Bartunov.
We still need to think about what it really means to WAL-log CREATE
TABLESPACE commands: we more or less have to put the absolute path
into those, but how to replay in a different context??

Tags:
----
REL8_0_STABLE

Modified Files:
--------------
pgsql/src/backend/commands:
dbcommands.c (r1.148.4.1 -> r1.148.4.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c.diff?r1=1.148.4.1&r2=1.148.4.2)
pgsql/src/include/commands:
dbcommands.h (r1.36 -> r1.36.4.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/commands/dbcommands.h.diff?r1=1.36&r2=1.36.4.1)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2005-03-23 00:36:15 pgsql: Remove: < < o Prevent conflicting SET options from being set <
Previous Message User Cmaj 2005-03-23 00:04:26 pgaccess - pgaccess: upgrading to tablelist 3.8