| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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>, Pgsql-Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql: Add command to use extended query protocol |
| Date: | 2022-11-11 15:09:39 |
| Message-ID: | 92b67b56-ff46-475f-5d53-83002f742568@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09.11.22 20:10, Daniel Verite wrote:
> Peter Eisentraut wrote:
>
>> Is there a use case for a global setting?
>
> I assume that we may sometimes want to use the
> extended protocol on all queries of a script, like
> pgbench does with --protocol=extended.
But is there an actual use case for this in psql? In pgbench, there are
scenarios where you want to test aspects of prepared statements, plan
caching, and so on. Is there something like that for psql?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-11-11 15:13:28 | Re: libpq support for NegotiateProtocolVersion |
| Previous Message | Peter Eisentraut | 2022-11-11 15:02:49 | Re: Meson doesn't define HAVE_LOCALE_T for mscv |