| From: | Albert Cervera i Areny <albert(at)nan-tic(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Peter Geoghegan <peter(at)2ndquadrant(dot)com>, "P(dot) Christeas" <xrg(at)linux(dot)gr> |
| Subject: | Re: [PATCH] Enforce that INSERT...RETURNING preserves the order of multi rows |
| Date: | 2012-10-21 05:50:47 |
| Message-ID: | 201210210750.47260.albert@nan-tic.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
A Dimecres, 17 d'octubre de 2012 19:13:47, Merlin Moncure va escriure:
> On Wed, Oct 17, 2012 at 9:29 AM, Peter Geoghegan <peter(at)2ndquadrant(dot)com>
wrote:
> > On 17 October 2012 14:53, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> >> Is that defined in the standard?
> >
> > RETURNING isn't even defined in the standard.
>
> Right: Point being, assumptions based on implementation ordering are
> generally to be avoided unless they are explicitly defined in the
> standard or elsewhere.
I don't see how one could use RETURNING if result is not ensured to be in the
same order as the tuples supplied. What's the use of RETURNING supplying data
in random order?
--
Albert Cervera i Areny
http://www.NaN-tic.com
Tel: +34 93 553 18 03
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2012-10-21 06:12:27 | Re: [PATCH] Enforce that INSERT...RETURNING preserves the order of multi rows |
| Previous Message | Guillaume Lelarge | 2012-10-20 21:41:15 | Re: Bug in -c CLI option of pg_dump/pg_restore |