Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Rob Sargent <robjsargent@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Double prepare
Date: Sat, 16 May 2026 08:07:01 -0600
Message-Id: <02D2D7C5-7932-4030-B65A-4BECB645E9F0@gmail.com>
References: <1495292.1778939187@sss.pgh.pa.us>
Cc: Igor Korot <ikorot01@gmail.com>,
 "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
In-Reply-To: <1495292.1778939187@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/02D2D7C5-7932-4030-B65A-4BECB645E9F0%40gmail.com>
Precedence: bulk


> On May 16, 2026, at 7:46=E2=80=AFAM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> =EF=BB=BFIgor Korot <ikorot01@gmail.com> writes:
>> Is there a way to see if the query has been prepared already (in libpq)?
>=20
> Use the pg_prepared_statements view.  I don't think libpq keeps any
> client-side state about this.
>=20
>> Or is it better to run for all known parameterized queries
>> in the very beginning of the program and just execute them when needed?
>=20
> Very probably.  Querying every time would be
> expensive.
>=20
If I am following correctly, one may query pg_prepared_statements with a spe=
cific query in hand. Should it not then be possible to cache that query as h=
aving been planned/prepared and proceed accordingly?

Might there be value in calling PQprepare as late as possible against most u=
p-to-dare data?


>   =20