Skip site navigation (1) Skip section navigation (2)

Re: BUG #6572: The example of SPI_execute is bogus

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: BUG #6572: The example of SPI_execute is bogus
Date: 2012-04-14 21:48:31
Message-ID: CA+TgmoZ5eK8rBhW3EttfJ7bLWKuXm48ei2ZROYFF-p6cazkzbA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
On Sat, Apr 14, 2012 at 12:15 PM, Peter Eisentraut <peter_e(at)gmx(dot)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(dot)stehule(at)gmail(dot)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

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-04-14 21:54:29
Subject: Re: Different gettext domain needed for error context
Previous:From: Jay LevittDate: 2012-04-14 21:34:36
Subject: Re: Last gasp

pgsql-bugs by date

Next:From: Boszormenyi ZoltanDate: 2012-04-15 09:14:38
Subject: Re: BUG #6572: The example of SPI_execute is bogus
Previous:From: Pavel StehuleDate: 2012-04-14 17:01:24
Subject: Re: BUG #6572: The example of SPI_execute is bogus

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group