Re: [HACKERS] drop before create in pg_dump - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] drop before create in pg_dump
Date
Msg-id 199901180451.XAA09348@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] drop before create in pg_dump  (Brook Milligan <brook@trillium.NMSU.Edu>)
List pgsql-hackers
>    Brook Milligan <brook@trillium.NMSU.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?

-c for clean.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom
Date:
Subject: Re: [HACKERS] Postgres Speed or lack thereof
Next
From: Vadim Mikheev
Date:
Subject: Re: [HACKERS] Postgres Speed or lack thereof