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

From Robert Treat
Subject Re: "truncate all"?
Date
Msg-id 1060016013.22273.1812.camel@camel
Whole thread Raw
In response to Re: "truncate all"?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: "truncate all"?
List pgsql-hackers
On Mon, 2003-08-04 at 12:19, Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > This this a TODO?  Keep in mind if we follow the syntax of VACUUM and
> > (7.4) CLUSTER, that the all-database truncate would just be "TRUNACATE".
> > That seems very risky to me.  I wonder if the risk is worth adding this
> > feature.
> 
> 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.
> 

Actually there seems to be an ancillary issue here:

21809=# truncate exception;
ERROR:  TRUNCATE cannot be used as table exception_notice_map references
this one via foreign key constraint $1
21809=# TRUNCATE exception_notice_map ;
TRUNCATE TABLE
21809=# truncate exception;
ERROR:  TRUNCATE cannot be used as table exception_notice_map references
this one via foreign key constraint $1
21809=# select count(*) from exception_notice_map;count 
-------    0
(1 row)

21809=# 

Robert Treat
-- 
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Thread-safe configuration option appears to misfunction
Next
From: Lamar Owen
Date:
Subject: Re: problem with RH7.3 Pg7.3.4 binaries