public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jelte Fennema-Nio <[email protected]>
To: Nathan Bossart <[email protected]>
Cc: Jacob Champion <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: alert clients when prepared statements are deallocated
Date: Sat, 6 Jun 2026 00:24:48 +0200
Message-ID: <CAGECzQRwr3yFmh1Hf9wyyYR0DjuSi0ZCiWHvYyY4pUp_ALF1bg@mail.gmail.com> (raw)
In-Reply-To: <aiNHmeERanDZViYv@nathan>
References: <ahm_4eOKkkKJ3Gds@nathan>
<CAOYmi+msZYr=NhBmf-Tg3h3ZHoQjMzp-50ByFqo2A8XDKd-eHQ@mail.gmail.com>
<CAGECzQQCKSogfz=Dqkf-+1GA13yATMu34CMU9Yqo13KXgmkW8Q@mail.gmail.com>
<aiNHmeERanDZViYv@nathan>
On Sat, Jun 6, 2026, 00:03 Nathan Bossart <[email protected]> wrote:
> Do we need to guard who can create protocol-level statements? And if so,
> how would we do that?
>
I think the only thing we'd need to guard against is a libpq user messing
with libpq its own internal protocol-level namespace, let's call that
"pqnamespace" for now. We'd add a new version of PQsendPrepare that would
take a namespace, but we'd make that return an error if a user of libpq
passed pqnamespace as the namespace argument. Similarly for the new
PQsendClosePrepared variant that takes a namespace. That way we'd reserve
that namespace.
>
view thread (13+ messages)
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: alert clients when prepared statements are deallocated
In-Reply-To: <CAGECzQRwr3yFmh1Hf9wyyYR0DjuSi0ZCiWHvYyY4pUp_ALF1bg@mail.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