Re: "truncate all"?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, shridhar_daithankar(at)persistent(dot)co(dot)in, pgsql-hackers(at)postgresql(dot)org
Subject: Re: "truncate all"?
Date: 2003-08-17 04:17:55
Message-ID: 200308170417.h7H4HtA07953@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-08-17 04:18:20 Re: "truncate all"?
Previous Message Stephan Szabo 2003-08-17 03:49:27 Re: Question with hashed IN