From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Infor Gates <info_gates(at)yahoo(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_restore |
Date: | 2006-06-18 05:06:36 |
Message-ID: | 25775.1150607196@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Infor Gates <info_gates(at)yahoo(dot)com> writes:
> I am having the impression that pg_restore would over-rides the "old"
> data with the current one. Is my thinking wrong?
Yeah. By default, pg_restore will issue a CREATE TABLE (which of course
fails if the table already exists) followed by COPY (which just tries to
insert data in addition to what might be there already).
There's a command line option to ask pg_restore to try to DROP TABLE
before doing the CREATE TABLE. By and large, though, that's a bad way
to proceed unless you are specifically trying to merge two databases.
The fast and easy way to proceed is to DROP DATABASE, CREATE a fresh
empty database, and pg_restore into that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ravindra Guravannavar | 2006-06-18 08:45:57 | clustering takes too long! |
Previous Message | Infor Gates | 2006-06-18 02:55:41 | Re: pg_restore |