| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16419: wrong parsing BC year in to_date() function |
| Date: | 2020-09-30 22:36:56 |
| Message-ID: | 20200930223656.GH26841@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Sep 30, 2020 at 06:10:38PM -0400, Robert Haas wrote:
> On Wed, Sep 30, 2020 at 5:35 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > By that logic, we should never fix any bug in a back branch.
>
> No, by that logic, we should not change any behavior in a back-branch
> upon which a customer is plausibly relying. No one relies on a certain
> query causing a server crash, for example, or a cache lookup failure,
> so fixing those things can only help people. But there is no reason at
> all why someone shouldn't be relying on this very old and
> long-established behavior not to change in a minor release.
That is an interesting distinction.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-09-30 23:26:55 | Re: BUG #16419: wrong parsing BC year in to_date() function |
| Previous Message | Tom Lane | 2020-09-30 22:36:37 | Re: BUG #16419: wrong parsing BC year in to_date() function |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-09-30 22:43:17 | Re: Improving connection scalability: GetSnapshotData() |
| Previous Message | Tom Lane | 2020-09-30 22:36:37 | Re: BUG #16419: wrong parsing BC year in to_date() function |