| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: default result formats setting |
| Date: | 2020-11-09 10:10:52 |
| Message-ID: | d2d18806-9dce-8207-5fa6-635434ad02d7@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-11-05 22:03, Peter Eisentraut wrote:
>> Independently of that, how would you implement "says otherwise" here,
>> ie do a single-query override of the session's prevailing setting?
>> Maybe the right thing for that is to define -1 all the way down to the
>> protocol level as meaning "use the session's per-type default", and
>> then if you don't want that you can pass 0 or 1. An advantage of that
>> is that you couldn't accidentally break an application that wasn't
>> ready for this feature, because it would not be the default to use it.
> Yeah, that sounds a lot better. I'll look into that.
Here is a new patch updated to work that way. Feels better now.
--
Peter Eisentraut
2ndQuadrant, an EDB company
https://www.2ndquadrant.com/
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Add-default_result_formats-setting.patch | text/plain | 11.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2020-11-09 10:22:56 | Re: pg_upgrade analyze script |
| Previous Message | Magnus Hagander | 2020-11-09 09:39:21 | Re: Useless string ouput in error message |