| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Pgsql-Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql: Add command to use extended query protocol |
| Date: | 2022-11-08 12:02:17 |
| Message-ID: | 01243e67-ef11-4c3a-90e7-c8a203e827da@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David G. Johnston wrote:
> I would keep the \gp meta-command to force extended mode regardless
> of whether the query itself requires it.
+1
> A pset variable to control the default seems reasonable as well.
> The implication would be that if you set that pset variable there is
> no way to have individual commands use simple query mode directly.
+1 except that it would be a \set variable for consistency with the
other execution-controlling variables. \pset variables control only
the display.
BTW if we wanted to auto-detect that a query requires binding or the
extended query protocol, we need to keep in mind that for instance
"PREPARE stmt AS $1" must pass without binding, with both the simple
and the extended query protocol.
Best regards,
--
Daniel Vérité
https://postgresql.verite.pro/
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amul Sul | 2022-11-08 12:07:20 | Re: Tables not getting vacuumed in postgres |
| Previous Message | Amit Kapila | 2022-11-08 11:49:53 | Re: Perform streaming logical transactions by background workers and parallel apply |