| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org>, "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>, Pgsql-Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql: Add command to use extended query protocol |
| Date: | 2022-11-08 12:39:14 |
| Message-ID: | a101c6b9-96ac-e309-fdab-ab74f6cc6a53@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08.11.22 13:02, Daniel Verite wrote:
>> 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.
Is there a use case for a global setting?
It seems to me that that would be just another thing that a
super-careful psql script would have to reset to get a consistent
starting state.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karthik Jagadish (kjagadis) | 2022-11-08 12:41:09 | Re: Tables not getting vacuumed in postgres |
| Previous Message | Peter Eisentraut | 2022-11-08 12:37:20 | Re: psql: Add command to use extended query protocol |