Re: BUG #16419: wrong parsing BC year in to_date() function - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: BUG #16419: wrong parsing BC year in to_date() function
Date
Msg-id 20200930223656.GH26841@momjian.us
Whole thread Raw
In response to Re: BUG #16419: wrong parsing BC year in to_date() function  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: BUG #16419: wrong parsing BC year in to_date() function  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@sss.pgh.pa.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@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16419: wrong parsing BC year in to_date() function
Next
From: Andres Freund
Date:
Subject: Re: Improving connection scalability: GetSnapshotData()