| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx |
| Date: | 2025-06-18 07:15:07 |
| Message-ID: | CAGECzQSP2=TmJHvnMm0T_88ERgWm9BDz1my0F_EqyX+Oexsg=Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 18 Jun 2025 at 08:23, Anthonin Bonnefoy
<anthonin(dot)bonnefoy(at)datadoghq(dot)com> wrote:
>
> On Tue, Jun 17, 2025 at 4:05 PM Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
> >
> > Agreed. My vote is for \closeprepared as that aligns with the libpq function.
>
> Since \bind_named is also new, we can also rename it to make it
> consistent with close meta-command. So what about renaming \bind_named
> to \bindprepared and \close to \closeprepared?
I think I still prefer \bind_named or maybe \bindnamed (depending on
what our policy for underscores in \ commands is). For that command it
should differentiate from the already existing \bind command, which is
also for prepared statements, just not for "named" prepared
statements. While close needs to differentiate from close for portals
vs close for prepared statements.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2025-06-18 07:25:32 | RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly |
| Previous Message | Jelte Fennema-Nio | 2025-06-18 07:11:15 | Re: Huge commitfest app update upcoming: Tags, Draft CF, Help page, and automated commitfest creat/open/close |