From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: dynamic result sets support in extended query protocol |
Date: | 2021-03-15 13:56:25 |
Message-ID: | d0840629-c875-a90b-e114-a4cdc91e2255@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Peter,
On 12/30/20 9:33 AM, Peter Eisentraut wrote:
> On 2020-10-09 20:46, Andres Freund wrote:
>> Is there really a good reason for forcing the client to issue
>> NextResult, Describe, Execute for each of the dynamic result sets? It's
>> not like there's really a case for allowing the clients to skip them,
>> right? Why aren't we sending something more like
>>
>> S: CommandPartiallyComplete
>> S: RowDescription
>> S: DataRow...
>> S: CommandPartiallyComplete
>> S: RowDescription
>> S: DataRow...
>> ...
>> S: CommandComplete
>> C: Sync
>
> I want to post my current patch, to keep this discussion moving.
CFBot reports that tests are failing, although the patch applies.
Also, you dropped all the driver authors from the thread. Not sure if
that was intentional, but you might want to add them back if you need
their input.
Regards,
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2021-03-15 14:05:54 | Re: documentation fix for SET ROLE |
Previous Message | Avinash Kumar | 2021-03-15 13:56:14 | Re: Postgres crashes at memcopy() after upgrade to PG 13. |