Re: BUG #3331: Database Restoring problem - Mailing list pgsql-bugs

From Larry Rosenman
Subject Re: BUG #3331: Database Restoring problem
Date
Msg-id 7E9866EA-2593-49EC-BF17-E347A95D64E8@lerctr.org
Whole thread Raw
In response to BUG #3331: Database Restoring problem  ("sajish" <sajishdaniel@yahoo.com>)
List pgsql-bugs
On Jun 2, 2007, at 10:32 AM, sajish wrote:

>
> The following bug has been logged online:
>
> Bug reference:      3331
> Logged by:          sajish
> Email address:      sajishdaniel@yahoo.com
> PostgreSQL version: 7.3
> Operating system:   Redhad Linux
> Description:        Database Restoring problem
> Details:
>
> Get errors on Restore database via Pg_Restore or psql
>
> Error: Relation 'table name' already exist
>
>
> i want to over write all tables when attempt to restore a
> database
>

look at the -c (--clean) option to pg_restore (assuming you are
dealing with a -Fc dump).


> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match

--
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 512-248-2683                 E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893

pgsql-bugs by date:

Previous
From: "sajish"
Date:
Subject: BUG #3331: Database Restoring problem
Next
From: Neil Conway
Date:
Subject: Re: minor issue - one semicolumn too many in the docs