Re: about truncate - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: about truncate
Date
Msg-id 87bpucn15z.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: about truncate  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: about truncate  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:

> On Mon, 2009-01-12 at 11:43 +0200, Peter Eisentraut wrote:
>> Peter Eisentraut wrote:
>> > Tom Lane wrote:
>> >> +1 for making TRUNCATE and LOCK support ONLY.
>> > 
>> > Patch attached.
>> 
>> This was committed.
>
> Please could we put in a GUC to allow that to be toggled in this release

That seems like it would just be putting off the pain. It doesn't make it any
easier to migrate in the end.

> and warning issued for non-optional behaviour change in following
> release? 

We do print INFO messages when drops cascade. We could print similar messages
when DDL applies recursively by default. (We can't do DML since it would fill
logs quickly). That seems reasonable to me.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services!


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Proposal: new border setting in psql
Next
From: Peter Eisentraut
Date:
Subject: Re: WIP: Automatic view update rules