On Thu, Apr 30, 2009 at 3:50 PM, Jaime Casanova <jcasa...@systemguards.com.ec> wrote: > On Thu, Apr 30, 2009 at 2:58 AM, Fujii Masao <masao.fu...@gmail.com> wrote: >> Hi, >> >> Does anyone know why a tablespace directory isn't automatically >> created in recovery? I think that it's troublesome to create all the >> directories before recovery. >> > > i guess it's because you need an absolute path to create tablespaces > and the appropiate path could not exist in the other machine (assuming > you are using recovery for warm standby or because you are recreating > a database after reinstall your server). >
From the caveats section in http://www.postgresql.org/docs/8.3/static/continuous-archiving.html#BACKUP-PITR-RECOVERY: """ * CREATE TABLESPACE commands are WAL-logged with the literal absolute path, and will therefore be replayed as tablespace creations with the same absolute path. This might be undesirable if the log is being replayed on a different machine. It can be dangerous even if the log is being replayed on the same machine, but into a new data directory: the replay will still overwrite the contents of the original tablespace. To avoid potential gotchas of this sort, the best practice is to take a new base backup after creating or dropping tablespaces. """ -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL AsesorÃa y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
