| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Subject: | Re: query ID goes missing with extended query protocol |
| Date: | 2024-09-09 15:24:28 |
| Message-ID: | CA+Tgmob+JuFYyYijdgyqfaWgsukv6nCaf63uAfYJhJBX4ggcOg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 28, 2024 at 6:48 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> This is being discussed already on a different thread:
> - Thread: https://www.postgresql.org/message-id/CA+427g8DiW3aZ6pOpVgkPbqK97ouBdf18VLiHFesea2jUk3XoQ@mail.gmail.com
> - CF entry: https://commitfest.postgresql.org/49/4963/
>
> There is a patch proposed there, that attempts to deal with the two
> cases of a portal where ExecutorRun() is called once while holding a
> tuplestore and where ExecutorRun() is called multiple times. A few
> approaches have been discussed for the tests, where the new psql
> metacommands added in d55322b0da60 should become handy. That's on my
> TODO spreadsheet of things to look at, but I did not come back to it
> yet.
That's interesting, but it sort of seems like it's reinventing the
wheel, vs. the one-line change that I proposed.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nazir Bilal Yavuz | 2024-09-09 15:25:07 | Re: Use read streams in pg_visibility |
| Previous Message | Tom Lane | 2024-09-09 14:48:30 | Re: Retire support for OpenSSL 1.1.1 due to raised API requirements |