Re: PL/pgSQL's "open cur for execute" provides workarouned... Re: cursors with prepared statements

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Bryn Llewellyn <bryn(at)yugabyte(dot)com>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: PL/pgSQL's "open cur for execute" provides workarouned... Re: cursors with prepared statements
Date: 2023-04-16 18:39:15
Message-ID: 3d1058fe-ac68-fbbe-e79e-d07d97d05638@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 4/16/23 11:02, Bryn Llewellyn wrote:> statement fails but doing this
using PL/pgSQL succeeds.
>
> What's going on under the covers?

Pretty sure:

https://www.postgresql.org/docs/current/spi.html

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message FOUTE K. Jaurès 2023-04-16 18:47:28 Re: Call a Normal function inside a Trigger Function
Previous Message Bryn Llewellyn 2023-04-16 18:02:03 PL/pgSQL's "open cur for execute" provides workarouned... Re: cursors with prepared statements