From: | Federico <cfederico87(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, John Howroyd <jdhowroyd(at)googlemail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Guidance on INSERT RETURNING order |
Date: | 2023-04-15 14:08:40 |
Message-ID: | CAN19dyfb8aPqSgsMpSEZNA85bu-JH1+NpUHccWe09FbSgKt0Mw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, 15 Apr 2023 at 15:40, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Federico <cfederico87(at)gmail(dot)com> writes:
> > I think the tuple order would not be connected to the values, but be
> > determined by the input order of the rows in the insert. So when using
> > INSERT ... SELECT the tuple_order value would be determined by the
> > output of the select, using the same logic as ROW_NUMBER.
>
> We already rejected the idea that INSERT must preserve the order of
> the incoming tuples. Please don't re-propose it with different
> wording.
>
> regards, tom lane
That was not my intention, what I meant is that the hypothetical
inserted.tuple_order in case of insert .. select would be determined
by the output order of the select. Insert would be free to insert the
row as it pleases.
Sorry if it wasn't clear.
Best
Federico
From | Date | Subject | |
---|---|---|---|
Next Message | Arquimedes Aguirre | 2023-04-15 14:39:02 | RE: FW: Error! |
Previous Message | Tom Lane | 2023-04-15 13:40:44 | Re: Guidance on INSERT RETURNING order |