| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Brendan Jurd <direvus(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Florian Pflug <fgp(at)phlo(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL) |
| Date: | 2013-04-08 14:41:39 |
| Message-ID: | CAM-w4HM9EqAtcJ5AMYpPbGP+4LY=TjcSEn13X1GGReA87kZicQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 4, 2013 at 4:10 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> The only reasonable answer for this (a provably used, non-security,
> non-standards violating, non-gross functionality breakage case) is
> *zero*. Our historically cavalier attitude towards compatibility
> breakage has been an immense disservice to our users and encourages
> very bad upgrade habits and is, IMNSHO, embarrassing.
>
The flip side of this is that the ability to make improvements freely is
one of the biggest strengths of free software over commercial software.
Oracle and Microsoft invest *tons* of money in maintaining huge libraries
of backward compatibility code and drastically limits their ability to keep
making improvements.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-04-08 14:42:30 | Re: pg_dump with postgis extension dumps rules separately |
| Previous Message | Tom Lane | 2013-04-08 14:36:26 | Re: [COMMITTERS] pgsql: Get rid of USE_WIDE_UPPER_LOWER dependency in trigram constructi |