Re: Remove array_nulls?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(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-18 17:10:14
Message-ID: 20151218171014.GC28035@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-12-18 12:06:43 -0500, Robert Haas wrote:
> Well, Tom, Alvaro, and I all pretty much said that removing things
> when it's blocking further development makes sense, but that there's
> no hurry to remove anything else. That sounds like what you are
> saying, too. So what's the actual disagreement here?

I'm saying that 10 year deprecation periods don't make sense. Either we
decide to remove the compat switch because we dislike it for $reasons,
in which case it should be removed sooner. Or we decide to keep the
switch indefinitely.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-12-18 17:10:33 Re: Remove array_nulls?
Previous Message Robert Haas 2015-12-18 17:09:43 Re: Freeze avoidance of very large table.