Postgres Pro
Downloads
Home   >   mailing lists

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

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

From
tgl@svr1.postgresql.org (Tom Lane)
Date:
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)

Re: pgsql: WAL must log CREATE and DROP DATABASE operations

From
Bruce Momjian
Date:
Added to TODO:

* Allow WAL replay of CREATE TABLESPACE to work when the directory
  structure on the recovery computer is different from the original


---------------------------------------------------------------------------

Tom Lane wrote:
> 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)
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073