Re: query ID goes missing with extended query protocol
От | Robert Haas |
---|---|
Тема | Re: query ID goes missing with extended query protocol |
Дата | |
Msg-id | CA+Tgmob+JuFYyYijdgyqfaWgsukv6nCaf63uAfYJhJBX4ggcOg@mail.gmail.com обсуждение исходный текст |
Ответ на | query ID goes missing with extended query protocol (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-hackers |
On Wed, Aug 28, 2024 at 6:48 PM Michael Paquier <michael@paquier.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
В списке pgsql-hackers по дате отправления: