From: | Larry Rosenman <ler(at)lerctr(dot)org> |
---|---|
To: | "sajish" <sajishdaniel(at)yahoo(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #3331: Database Restoring problem |
Date: | 2007-06-02 13:38:14 |
Message-ID: | 7E9866EA-2593-49EC-BF17-E347A95D64E8@lerctr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)yahoo(dot)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(at)lerctr(dot)org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2007-06-02 15:16:08 | Re: minor issue - one semicolumn too many in the docs |
Previous Message | Frank van Vugt | 2007-06-02 12:25:47 | minor issue - one semicolumn too many in the docs |