Re: default result formats setting - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: default result formats setting
Date
Msg-id d2d18806-9dce-8207-5fa6-635434ad02d7@2ndquadrant.com
Whole thread Raw
In response to Re: default result formats setting  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: default result formats setting  (Andrew Dunstan <andrew@dunslane.net>)
List 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

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Useless string ouput in error message
Next
From: Magnus Hagander
Date:
Subject: Re: pg_upgrade analyze script