| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: alert clients when prepared statements are deallocated |
| Date: | 2026-06-05 22:24:48 |
| Message-ID: | CAGECzQRwr3yFmh1Hf9wyyYR0DjuSi0ZCiWHvYyY4pUp_ALF1bg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jun 6, 2026, 00:03 Nathan Bossart <nathandbossart(at)gmail(dot)com> 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.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Baji Shaik | 2026-06-05 23:44:59 | Re: [PATCH] Fix memory leak in pgstat_progress_parallel_incr_param() |
| Previous Message | Daniel Gustafsson | 2026-06-05 22:22:38 | Re: Fix OAuth validator docs for error_detail on internal errors |