| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Dave Cramer <davecramer(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CommandStatus from insert returning when using a portal. |
| Date: | 2023-07-12 20:31:04 |
| Message-ID: | CAKFQuwYBALhvo4anw3sqk_AHRO+9XR1vL5g_BWsPGK8CVcCy5w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 12, 2023 at 1:03 PM Dave Cramer <davecramer(at)gmail(dot)com> wrote:
>
> INSERT INTO test_table (cnt) VALUES (1), (2) RETURNING id
>
> if a portal is used to get the results then the CommandStatus
>
IIUC the portal is not optional if you including the RETURNING clause.
There is no CommandStatus message in the protocol, the desired information
is part of the command tag returned in the CommandComplete message. You
get that at the end of the command, which has been defined as when any
portal produced by the command has been fully executed.
You probably should add your desire to the Version 4 protocol ToDo on the
wiki.
https://wiki.postgresql.org/wiki/Todo#Wire_Protocol_Changes_.2F_v4_Protocol
If that ever becomes an active project working through the details of that
list for desirability and feasibility would be the first thing to happen.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2023-07-12 20:37:14 | Re: CommandStatus from insert returning when using a portal. |
| Previous Message | Dave Cramer | 2023-07-12 20:03:15 | CommandStatus from insert returning when using a portal. |