public inbox for [email protected]
help / color / mirror / Atom feedFrom: David G. Johnston <[email protected]>
To: Shay Rojansky <[email protected]>
Cc: Pg Hackers <[email protected]>
Subject: Re: Document ordering guarantees on INSERT/UPDATE RETURNING clause
Date: Sat, 26 Feb 2022 06:25:22 -0700
Message-ID: <CAKFQuwZYmqiRq5nTh8ghcfSZ0Qsx6AHbzNArMLLEX0xfeSwLOg@mail.gmail.com> (raw)
In-Reply-To: <CADT4RqCvuRucgqZjKJypsjAPeEg3QBDND4z1JW4mX=X9fWFkpg@mail.gmail.com>
References: <CADT4RqCvuRucgqZjKJypsjAPeEg3QBDND4z1JW4mX=X9fWFkpg@mail.gmail.com>
On Sat, Feb 26, 2022 at 5:42 AM Shay Rojansky <[email protected]> wrote:
> FWIW I've received feedback from a SQL Server engineer that one definitely
> should *not* depend on such ordering there, and that future optimizations
> (e.g. parallel insertion of many rows) could result in row ordering which
> differs from the lexical ordering of the VALUES clause.
>
> That seems very reasonable; if the situation is similar on PostgreSQL,
> then I'd suggest making that very clear in the INSERT[2] and UPDATE[3] docs.
>
There is clearly no mention of such a guarantee in our documentation.
David J.
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Document ordering guarantees on INSERT/UPDATE RETURNING clause
In-Reply-To: <CAKFQuwZYmqiRq5nTh8ghcfSZ0Qsx6AHbzNArMLLEX0xfeSwLOg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox