Re: [BUGS] BUG #6572: The example of SPI_execute is bogus - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [BUGS] BUG #6572: The example of SPI_execute is bogus
Date
Msg-id CA+TgmoZ5eK8rBhW3EttfJ7bLWKuXm48ei2ZROYFF-p6cazkzbA@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] BUG #6572: The example of SPI_execute is bogus  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Sat, Apr 14, 2012 at 12:15 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On lör, 2012-04-14 at 08:23 -0400, Robert Haas wrote:
>> On Sat, Apr 14, 2012 at 3:27 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> >> It has a lot of sense.  Without it, it's very difficult to do logical
>> >> replication on a table with no primary key.
>> >>
>> >> (Whether or not people should create such tables in the first place
>> >> is, of course, beside the point.)
>> >
>> > I am not against to functionality - I am against just to syntax DELETE
>> > FROM tab LIMIT x
>> >
>> > because is it ambiguous what means: DELETE FROM tab RETURNING * LIMIT x
>>
>> What's ambiguous about that?
>
> I suppose one could wonder whether the LIMIT applies to the deleting or
> just the returning.

I suppose.  I had in mind it would apply to both.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Jay Levitt
Date:
Subject: Re: Last gasp
Next
From: Tom Lane
Date:
Subject: Re: Different gettext domain needed for error context