| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: dynamic result sets support in extended query protocol |
| Date: | 2022-12-22 19:39:21 |
| Message-ID: | 20221222193921.yaosmvvoymncxyl2@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-Dec-21, Alvaro Herrera wrote:
> I suppose that in order for this to work, we would have to find another
> way to "advance" the queue that doesn't rely on the status being
> PGASYNC_READY.
I think the way to make this work is to increase the coupling between
fe-exec.c and fe-protocol.c by making the queue advance occur when
CommandComplete is received. This is likely more correct protocol-wise
than what we're doing now: we would consider the command as done when
the server tells us it is done, rather than relying on internal libpq
state.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2022-12-22 19:45:57 | Re: Schema variables - new implementation for Postgres 15 (typo) |
| Previous Message | Peter Geoghegan | 2022-12-22 19:39:10 | Re: New strategies for freezing, advancing relfrozenxid early |