On Wed, 23 Mar 2005, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > On Tue, 2005-03-22 at 21:42 -0500, Bruce Momjian wrote:
> >> Is this a TODO?
>
> > Yes, it is.
>
> > In my experience, most people create only a single Database, then define
> > their Tablespaces (or change them rarely, if ever). So I've always
> > regarded CREATE DATABASE and TABLESPACE as lower priority items. I'd
> > always recommend taking another full backup immediately following such
> > changes, rather than rely on everything working in the rollforward. That
> > was true with PITR and similarly true with log shipping based upon PITR.
>
[snip]
> The hard part is CREATE TABLESPACE, and the reason it's hard is that
> someone might possibly want the tablespace to be located at a different
> place on the recipient machine than it is on the master. I do not see a
> reasonable way to support that at the moment. For the moment I think we
> should just document that as a gotcha, and make a TODO item to find a
> way to do it.
Here is a docs patch which adds a note to the section on PITR.
Gavin
diff -rN -c old-mainline/doc/src/sgml/backup.sgml
new-mainline/doc/src/sgml/backup.sgml
*** old-mainline/doc/src/sgml/backup.sgml 2005-03-24 13:54:22.000000000
+1100
--- new-mainline/doc/src/sgml/backup.sgml 2005-03-24 14:29:16.000000000
+1100
***************
*** 1123,1128 ****
--- 1123,1138 ----
such index after completing a recovery operation.
</para>
</listitem>
+ <listitem>
+ <para>
+ The <command>CREATE TABLESPACE</> command records the location of the
+ tablespace in WAL. This could be a problem if the WAL segments are
+ replayed on a different system to those that they were created on because
+ it is likely that the tablespace directory will not exist on the second
+ system. To avoid this, you should ensure that the path to the tablespace
+ exists on the secondary machine and has the correct permissions.
+ </para>
+ </listitem>
</itemizedlist>
</para>
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
