Re: "truncate all"? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: "truncate all"?
Date
Msg-id 200308170417.h7H4HtA07953@candle.pha.pa.us
Whole thread Raw
In response to Re: "truncate all"?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Added to TODO:
* Add TRUNCATE ... CASCADE


---------------------------------------------------------------------------

Josh Berkus wrote:
> Guys,
> 
> > I wouldn't care for that either.  The prior suggestion of "TRUNCATE tab
> > CASCADE" (to truncate any tables with FK dependencies on the original
> > target, instead of failing) seems more reasonable.
> 
> I agree with Tom ... even the idea of a "TRUNCATE ALL" makes me nervous.  If 
> we had such a feature, I'd advocate that it be superuser only.
> 
> As for "TRUNCATE CASCADE" or similar improvements, I agree that they could be 
> convenient ... but are easily worked around currently.   So I wouldn't object 
> to putting TRUNCATE CASCADE on the todo list, but would argue that it be left 
> to the people who asked for it to implement it.
> 
> As far as 
> 
> -- 
> Josh Berkus
> Aglio Database Solutions
> San Francisco
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Question with hashed IN
Next
From: Bruce Momjian
Date:
Subject: Re: "truncate all"?