| 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:02:01 |
| Message-ID: | 20151218170201.GB28035@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-12-16 19:01:40 -0500, Robert Haas wrote:
> Yeah, there's something to be said for that, although to be honest in
> most cases I'd prefer to wait longer. I wonder about perhaps
> planning to drop things after two lifecycles.
I don't really give a damn in this specific case. Seems to cost pretty
much nothing to continue having the GUC.
But I think in the more general case, which Tom seems to have brought up
as a point of policy, I think this is far to conservative. Yes, we owe
our users to not break their applications gratuitously. But we also owe
it to ourselves to keep development timeframes realistic, and not pay
overly much heed to people using seriously bad development and
maintenance practices.
It doesn't even benefit users really much delaying things that
long. Usually the migration costs, of fixing code previously kept
working by a GUC, increase over time, not decrease.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-12-18 17:05:16 | Re: Typo in the comment above heap_prepare_freeze_tuple() |
| Previous Message | Robert Haas | 2015-12-18 16:58:55 | Re: Refactoring speculative insertion with unique indexes a little |