Re: dynamic result sets support in extended query protocol - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: dynamic result sets support in extended query protocol
Date
Msg-id 525d517f-72ab-9488-211b-ad3cb0aea3a3@enterprisedb.com
Whole thread Raw
In response to Re: dynamic result sets support in extended query protocol  (vignesh C <vignesh21@gmail.com>)
Responses Re: dynamic result sets support in extended query protocol  (Zhihong Yu <zyu@yugabyte.com>)
List pgsql-hackers
rebased patch set

On 22.07.21 08:06, vignesh C wrote:
> On Tue, Jun 29, 2021 at 7:10 PM Peter Eisentraut
> <peter.eisentraut@enterprisedb.com> wrote:
>>
>> Here is an updated patch with some merge conflicts resolved, to keep it
>> fresh.  It's still pending in the commit fest from last time.
>>
>> My focus right now is to work on the "psql - add SHOW_ALL_RESULTS
>> option" patch (https://commitfest.postgresql.org/33/2096/) first, which
>> is pretty much a prerequisite to this one.  The attached patch set
>> contains a minimal variant of that patch in 0001 and 0002, just to get
>> this working, but disregard those for the purposes of code review.
>>
>> The 0003 patch contains comprehensive documentation and test changes
>> that can explain the feature in its current form.
> 
> One of the patch v3-0003-Dynamic-result-sets-from-procedures.patch
> does not apply on HEAD, please post an updated patch for it:
> Hunk #1 FAILED at 57.
> 1 out of 1 hunk FAILED -- saving rejects to file
> src/include/commands/defrem.h.rej
> 
> Regards,
> Vignesh
> 
> 


Attachment

pgsql-hackers by date:

Previous
From: "Bossart, Nathan"
Date:
Subject: Re: archive status ".ready" files may be created too early
Next
From: Alvaro Herrera
Date:
Subject: Re: reporting TID/table with corruption error