Re: [HACKERS] drop before create in pg_dump

From: Brook Milligan <brook(at)trillium(dot)NMSU(dot)Edu>
To: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] drop before create in pg_dump
Date: 1999-01-17 22:11:47
Message-ID: 199901172211.PAA05434@trillium.nmsu.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Brook Milligan <brook(at)trillium(dot)NMSU(dot)Edu> writes:
> pg_dump won't drop stuff before trying to create it; this makes
> dropping a single table (say) and recreating it difficult to automate
> since it is subject to error if all the stuff doesn't get dropped
> properly. The following patch causes pg_dump to emit DROP ...
> statements prior to emitting CREATE ... statements.

I think that ought to be driven by a switch to pg_dump ...
much of the time, I would *want* pg_dump's script to fail
if there's already an existing item of the given name.

A switch is fine. Is there any concensus as to what it should be,
since the two that come to mind (-D and -d) are both used?

Cheers,
Brook

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-01-18 00:07:36 Re: EXCEPT/INTERSECT for v6.4
Previous Message Tom Lane 1999-01-17 21:22:22 Re: [HACKERS] some patches for 6.4.2