Re: Remove array_nulls?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove array_nulls?
Date: 2015-12-17 21:31:01
Message-ID: CA+TgmoYHNKr_hbFuYyFP7Zbkaf3cdFMPFg4q0r2PZ8NAXKf7SQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 16, 2015 at 10:48 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> IIUC, that means supporting backwards compat. GUCs for 10 years, which seems
> a bit excessive. Granted, that's about the worse-case scenario for what I
> proposed (ie, we'd still be supporting 8.0 stuff right now).

Not to me. GUCs like array_nulls don't really cost much - there is no
reason to be in a hurry about removing them that I can see.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-12-17 21:56:48 Re: broken autocomplete in head
Previous Message Tomas Vondra 2015-12-17 21:28:41 Re: PATCH: postpone building buckets to the end of Hash (in HashJoin)