Re: [HACKERS] drop before create in pg_dump

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: brook(at)trillium(dot)NMSU(dot)Edu (Brook Milligan)
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] drop before create in pg_dump
Date: 1999-01-18 04:51:14
Message-ID: 199901180451.XAA09348@candle.pha.pa.us
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?

-c for clean.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vadim Mikheev 1999-01-18 04:54:44 Re: [HACKERS] Postgres Speed or lack thereof
Previous Message Tom Lane 1999-01-18 04:21:45 Re: [HACKERS] Postgres Speed or lack thereof