Re: [COMMITTERS] pgsql: Remove: * Allow database recovery

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Remove: * Allow database recovery
Date: 2004-11-08 16:48:04
Message-ID: 200411081648.iA8Gm4N26259@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Marc G. Fournier wrote:
> On Mon, 8 Nov 2004, Bruce Momjian wrote:
>
> > Marc G. Fournier wrote:
> >>
> >> Just curious, but in what sort of circumstance could this happen?
> >> Permissions problems, that sort of thing?
> >
> > Restoring a dump to another system that doesn't have the same
> > directories to create the tablespaces.
>
> 'k, that's what I thought, just wanted to clarify ... stupid question then
> ... if such a case happens, do we send a WARNING to let ppl know that the
> load didn't quite go as the dump went?

Yes, they get a warning because the tablespace create failed. When we
had a TABLESPACE clause in create (before default_tablespace), all the
CREATEs would fail leading to a useless restore.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2004-11-08 18:01:29 pgsql: Recommend that archive_command be coded to not overwrite existing
Previous Message Marc G. Fournier 2004-11-08 16:42:06 Re: [COMMITTERS] pgsql: Remove: * Allow database recovery

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2004-11-08 17:03:49 latest cygwin build failure
Previous Message Marc G. Fournier 2004-11-08 16:42:06 Re: [COMMITTERS] pgsql: Remove: * Allow database recovery