| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: about truncate |
| Date: | 2009-01-12 12:45:12 |
| Message-ID: | 87bpucn15z.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)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!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-01-12 12:48:46 | Re: WIP: Automatic view update rules |
| Previous Message | Alvaro Herrera | 2009-01-12 12:34:56 | Re: Proposal: new border setting in psql |