Re: Truncate if exists

From: Daniel Farina <daniel(at)heroku(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Sébastien Lardière <slardiere(at)hi-media(dot)com>, pgsql-hackers(at)postgresql(dot)org, cedric(at)2ndquadrant(dot)fr
Subject: Re: Truncate if exists
Date: 2012-10-09 21:31:10
Message-ID: CAAZKuFZpsuLNLzq7LLwg3ZKQU1JGmF75MY47XzXXfO0M7zEBGQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 9, 2012 at 2:04 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 9 October 2012 21:35, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>> On 10/9/12 5:09 AM, Simon Riggs wrote:
>>> Anyone want to check for any other missing IF EXISTS capability in other DDL?
>>
>> TRUNCATE is not really DDL. If we allow TRUNCATE IF EXISTS, what is
>> stopping someone from requesting DELETE IF EXISTS or INSERT IF EXISTS next?
>
> I'm not involved in the planning or justification for this patch, and
> have no opinion.
>
> I discussed applying it because it was an uncontentious patch. It
> clearly is not....

I also read Simon's approach as not a push for inclusion, but
defaulting to commit for smaller patches that basically look
mechanically legitimate with no objections to streamline
communication. Since pgsql-hackers has a good record objecting to
patches that require objection in a timely manner, I think that's
reasonable. The cost of revert would not be that high, either.

Clearly those conditions were not met, but I don't think it's
justified to jump on Simon for this approach on a patch like this.

--
fdr

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John R Pierce 2012-10-09 21:43:11 Re: pgxs problem...
Previous Message Simon Riggs 2012-10-09 21:04:04 Re: Truncate if exists