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+TgmoYL_GC=1OSpPFW=Qz_LVe6_y0x2qQ=GSgEx2NpFKYhPNw@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] BUG #6572: The example of SPI_execute is bogus  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses 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 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?

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: column name of pg_stat_replication.backend_start
Next
From: Robert Haas
Date:
Subject: Re: Patch: add timing of buffer I/O requests