| From: | Dave Cramer <davecramer(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | chap(at)anastigmatix(dot)net, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CommandStatus from insert returning when using a portal. |
| Date: | 2023-07-14 16:58:18 |
| Message-ID: | CADK3HHJKCpS-Fx-37ObLgM6VKdN-rwhbjNvgPobwiN7=AU8mqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
See attached pcap file
after the execute of the portal it returns INSERT 0 0
Dave Cramer
On Fri, 14 Jul 2023 at 12:57, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Fri, Jul 14, 2023 at 9:50 AM David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>>
>> Fixing that test in some manner and recompiling psql seems like it should
>> be the easiest way to produce a core-only test case.
>>
>>
> Apparently not - since it (ExecQueryUsingCursor) literally wraps the query
> in a DECLARE CURSOR SQL Command which prohibits INSERT...
>
> I suppose we'd have to write a psql equivalent of ExecQueryUsingPortal
> that iterates over via fetch to make this work...probably more than I'm
> willing to try.
>
> David J.
>
| Attachment | Content-Type | Size |
|---|---|---|
| cursor.pcap | application/octet-stream | 20.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | chap | 2023-07-14 17:39:21 | Re: CommandStatus from insert returning when using a portal. |
| Previous Message | David G. Johnston | 2023-07-14 16:56:49 | Re: CommandStatus from insert returning when using a portal. |