From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: odd problem ! |
Date: | 2005-03-24 05:19:47 |
Message-ID: | Pine.LNX.4.58.0503241618280.22704@linuxworld.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 23 Mar 2005, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)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
Attachment | Content-Type | Size |
---|---|---|
tablespace_log.diff | text/plain | 967 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-03-24 05:48:39 | Re: odd problem ! |
Previous Message | Bruce Momjian | 2005-03-24 05:15:53 | Re: fool-toleranced optimizer |