Re: [PATCH] Enforce that INSERT...RETURNING preserves the order of multi rows

From: Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Christopher Browne <cbbrowne(at)gmail(dot)com>
Subject: Re: [PATCH] Enforce that INSERT...RETURNING preserves the order of multi rows
Date: 2012-10-21 18:43:28
Message-ID: 20121021184328.GF30489@toroid.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 2012-10-21 14:27:39 -0400, tgl(at)sss(dot)pgh(dot)pa(dot)us wrote:
>
> Is that fundamentally an illegitimate optimization, and if so why?

I wouldn't say it's illegitimate. It's a bit less convenient for the
application programmer, and will surprise some people (even some who
know better than to expect SELECT to produce a particular row order).
That's all.

-- Abhijit

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2012-10-21 18:45:31 Re: [PATCH] Enforce that INSERT...RETURNING preserves the order of multi rows
Previous Message P. Christeas 2012-10-21 18:27:41 Re: [PATCH] Enforce that INSERT...RETURNING preserves the order of multi rows