| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: default result formats setting |
| Date: | 2021-03-24 14:49:33 |
| Message-ID: | CA+TgmoaxDj4pDADDvRuHXEez=DM5VrtpEjtHXB6RzgFGZQtvgg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 5, 2020 at 3:49 PM Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> We could also make it a protocol message, but it would essentially
> implement the same thing, just again separately. And then you'd have no
> support to inspect the current setting, test out different settings
> interactively, etc. That seems pretty wasteful and complicated for no
> real gain.
But ... if it's just a GUC, it can be set by code on the server side
that the client knows nothing about, breaking the client. That seems
pretty bad to me.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-03-24 14:50:50 | Re: pgsql: Move tablespace path re-creation from the makefiles to pg_regres |
| Previous Message | Tomas Vondra | 2021-03-24 14:47:54 | Re: PoC/WIP: Extended statistics on expressions |