On Tue, 2005-03-22 at 21:42 -0500, Bruce Momjian wrote:
> Tom Lane wrote:
> > Oleg Bartunov <oleg@sai.msu.su> writes:
> > >> This isn't a problem in normal use of course, but it'd be a serious
> > >> issue for someone engaging in WAL-shipping, if their backup postmaster
> > >> were living at a different absolute path. We probably need to think
> >
> > > right, this is normal situation if you backup to the same server.
> > > Not sure how it's usefull, but still
> >
> > >> about whether we can make CREATE DATABASE log only relative paths.
> >
> > > any problem ?
> >
> > I've committed a fix --- please check that it solves your problem.
> > (I have to leave for a few hours so I can't check it myself right away.)
> >
> > >> Log-shipping CREATE TABLESPACE commands is even more interesting :-(.
> > >> Not sure how to deal with that.
> >
> > > in general case it's impossible.
> >
> > Yeah :-( ... needs more thought.
>
> 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.
Best Regards, Simon Riggs
