Re: odd problem ! - Mailing list pgsql-hackers

From Gavin Sherry
Subject Re: odd problem !
Date
Msg-id Pine.LNX.4.58.0503241618280.22704@linuxworld.com.au
Whole thread Raw
In response to Re: odd problem !  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: odd problem !  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, 23 Mar 2005, Tom Lane wrote:

> Simon Riggs <simon@2ndquadrant.com> 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

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: fool-toleranced optimizer
Next
From: Tom Lane
Date:
Subject: Re: odd problem !