MIME-Version: 1.0
References: <ahm_4eOKkkKJ3Gds@nathan> <1689313.1780074543@sss.pgh.pa.us>
 <ahna7lre-xAn7DIS@nathan> <ah9VKGwwlgqF-hi7@nathan> <aiCZ60MNyTQ8_4BE@nathan>
In-Reply-To: <aiCZ60MNyTQ8_4BE@nathan>
From: Jacob Champion <jacob.champion@enterprisedb.com>
Date: Thu, 4 Jun 2026 16:56:04 -0700
Message-ID: 
 <CAOYmi+ndz7Dx5WdJu8zRPXLsA6U56jvcKnoT=ru2DhQtOKy=eA@mail.gmail.com>
Subject: Re: alert clients when prepared statements are deallocated
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAOYmi%2Bndz7Dx5WdJu8zRPXLsA6U56jvcKnoT%3Dru2DhQtOKy%3DeA%40mail.gmail.com>
Precedence: bulk

On Wed, Jun 3, 2026 at 2:17=E2=80=AFPM Nathan Bossart <nathandbossart@gmail=
.com> wrote:
> Hm.  So there's actually a pretty obvious problem here.  Say a user
> executes something like PQsendQuery(conn, "DISCARD ALL") and then tries t=
o
> execute an lo_* function (modified to use prepared statements) prior to
> consuming the result.  In that case, the callback won't be called in time
> and the LO function will fail.

Are you allowed to call lo_*/PQfn() in the middle of an operation like
that? I.e. does it work today?

--Jacob