Re: Remove array_nulls? - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Remove array_nulls?
Date
Msg-id 566F0327.5010904@BlueTreble.com
Whole thread Raw
In response to Re: Remove array_nulls?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Remove array_nulls?  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On 12/11/15 2:57 PM, Tom Lane wrote:
> Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
>> A quick doc search indicates this config was created in 9.0, though the
>> docs state it's for a change that happened in 8.2[1].
>
> Don't know what you're looking at, but the GUC is definitely there (and
> documented) in 8.2.
>
>> Is it time to remove this GUC?
>
> Perhaps, but I'd like to have a less ad-hoc process about it.  What's
> our policy for dropping backwards-compatibility GUCs?  Are there any
> others that should be removed now as well?

Perhaps it should be tied to bumping the major version number, which I'm 
guessing would happen next whenever we get parallel query execution. If 
we do that, a reasonable policy might be that a compatability GUC lives 
across no more than 1 major version bump (ie, we wouldn't remove 
something in 9.0 that was added in 8.4).
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Re: Logical replication and multimaster
Next
From: Kevin Grittner
Date:
Subject: Re: Another XML build issue