Re: bug in pg_restore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
Cc: "Jeffrey W(dot) Baker" <jwbaker(at)acm(dot)org>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org>
Subject: Re: bug in pg_restore
Date: 2002-01-19 00:34:15
Message-ID: 11130.1011400455@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> On 18 Jan 2002, Jeffrey W. Baker wrote:
>> I think there is a little bug in pg_restore. It says it can't restore
>> because the database doesn't exist, but then if I create the database it
>> says it can't proceed because the database DOES exist. The solution for
>> me was to omit the -C argument, but it looks like a bug to me:

> I think the intention is that with -C, the -d argument is the database
> to connect to before generating the create for the database that's
> specified in the dump, not the final name of the database.

Yeah. The 7.1 documentation is very confusing on this point.
I tried awhile ago to clean it up for 7.2. You might care to look at
http://developer.postgresql.org/docs/postgres/app-pgdump.html
http://developer.postgresql.org/docs/postgres/app-pgrestore.html
(there might be some stuff in there that's new for 7.2, but these
switches didn't change).

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jan Wieck 2002-01-19 01:06:32 Re: large file limitation
Previous Message Mitch Vincent 2002-01-18 23:49:43 Re: Need book on PHP and PostgreSQL