From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Brendan Jurd <direvus(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL) |
Date: | 2013-06-21 01:35:34 |
Message-ID: | 20130621013534.GD20417@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 20, 2013 at 06:28:07PM -0700, Josh Berkus wrote:
> Bruce,
>
> > Well, sometimes we underestimate the impact of changes, sometimes we
> > overestimate. The big problem is weighing the short-term problems of
> > change but not the long-term benefit of a change. This array problem
> > goes back to at least 2008:
> >
> > http://www.postgresql.org/message-id/28026.1224611437@sss.pgh.pa.us
> >
> > so we have at least five years of confusion by not changing it then. I
> > am not saying we need to change it, but do think we need to weigh both
> > issues.
>
> As much as I hate the current behavior (my first response was "yeah, fix
> those babies!"), I think we don't have a choice about creating new
> function names and then waiting three years to deprecate the old ones.
> We really can't afford to put obstacles in the way of people upgrading,
> especially over an issue as minor as this one.
Perhaps we need to mark the TODO item as "will not fix".
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Rijkers | 2013-06-21 01:38:24 | trgm regex index peculiarity |
Previous Message | Andres Freund | 2013-06-21 01:32:35 | Re: changeset generation v5-01 - Patches & git tree |