public inbox for pgsql-general@postgresql.org  

help / color / mirror / Atom feed

From: Rob Sargent <robjsargent@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Igor Korot <ikorot01@gmail.com>
Cc: pgsql-generallists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: Double prepare
Date: Sat, 16 May 2026 08:07:01 -0600
Message-ID: <02D2D7C5-7932-4030-B65A-4BECB645E9F0@gmail.com> (raw)
In-Reply-To: <1495292.1778939187@sss.pgh.pa.us>
References: <1495292.1778939187@sss.pgh.pa.us>



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

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


>    

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-general@postgresql.org
  Cc: robjsargent@gmail.com, tgl@sss.pgh.pa.us, ikorot01@gmail.com, pgsql-general@lists.postgresql.org
  Subject: Re: Double prepare
  In-Reply-To: <02D2D7C5-7932-4030-B65A-4BECB645E9F0@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox