Re: dynamic result sets support in extended query protocol

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Zhihong Yu <zyu(at)yugabyte(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>
Subject: Re: dynamic result sets support in extended query protocol
Date: 2022-01-12 10:20:55
Message-ID: 20220112102055.fn5gpnt2lw6ii35o@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Mon, Aug 30, 2021 at 02:11:34PM -0700, Zhihong Yu wrote:
> On Mon, Aug 30, 2021 at 1:23 PM Peter Eisentraut <
> peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>
> > rebased patch set
>
> + <term><literal>WITH RETURN</literal></term>
> + <term><literal>WITHOUT RETURN</literal></term>
> + <listitem>
> + <para>
> + This option is only valid for cursors defined inside a procedure.
>
> Since there are two options listed, I think using 'These options are' would
> be better.
>
> For CurrentProcedure(),
>
> + return InvalidOid;
> + else
> + return llast_oid(procedure_stack);
>
> The word 'else' can be omitted.

The cfbot reports that the patch doesn't apply anymore:
http://cfbot.cputube.org/patch_36_2911.log.

Since you mentioned that this patch depends on the SHOW_ALL_RESULTS psql patch
which is still being worked on, I'm not expecting much activity here until the
prerequirements are done. It also seems better to mark this patch as Waiting
on Author as further reviews are probably not really needed for now.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2022-01-12 10:30:07 Re: sepgsql logging
Previous Message Amit Kapila 2022-01-12 10:14:25 Re: 2022-01 Commitfest