| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ToDo: pg_backup - using a conditional DROP |
| Date: | 2011-11-16 14:42:46 |
| Message-ID: | 1321454566.30837.1.camel@fsopti579.F-Secure.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On tis, 2011-11-15 at 22:27 -0500, Tom Lane wrote:
> Now, --clean using DROP IF EXISTS would be targeted at, um, what case?
> I guess the idea is to be able to load into a database that sort of
> mostly shares the same schema as the one you dumped from, only it's
> not the same (if it were the same, you'd not need IF EXISTS).
What about a schema that is nominally the same, but some object is
missing, because some earlier attempt to clean things up, or because
it's an earlier version of the schema, or because of some batch jobs
make things come and go.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-11-16 14:47:38 | Re: strict aliasing |
| Previous Message | Rudyar | 2011-11-16 14:38:36 | how to get tuple |