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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, 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:54:10
Message-ID: 508444D2.4020508@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 10/21/2012 02:47 PM, Andres Freund wrote:
> On Sunday, October 21, 2012 08:45:31 PM Andrew Dunstan wrote:

>>
>> I guess in such a case I'd be inclined to precompute the id values and
>> then supply them in the values clause. That means two round trips rather
>> than one.
> Which will fail should we get upsert one day...
>

Sufficient unto the day is the evil thereof. It seems premature to worry
about it now.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-10-21 19:08:05 Re: Re: [PATCH] Enforce that INSERT...RETURNING preserves the order of multi rows
Previous Message Andres Freund 2012-10-21 18:47:27 Re: [PATCH] Enforce that INSERT...RETURNING preserves the order of multi rows