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 20200930202016.GG26841@momjian.us
Whole thread Raw
In response to 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 03:11:06PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > On Wed, Sep 30, 2020 at 02:50:31PM -0400, Tom Lane wrote:
> >> Actually, I was just finishing up back-patching the patch I posted
> >> yesterday.  I think we should just fix it, not document that it's
> >> broken.
> 
> > Agreed, that's what I wanted.  You stated in a later email you couldn't
> > convince yourself of the backpatch, which is why I asked.
> 
> Oh, I see where our wires are crossed.  I meant that I couldn't
> convince myself to back-patch the make_timestamp() change.
> (I'm still willing to listen to an argument to do so, if anyone
> wants to make one --- but that part feels more like a feature
> addition than a bug fix.)

OK, at least this is addressed fully in PG 14 and beyond.

-- 
  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: Rahila Syed
Date:
Subject: Re: [PATCH] Automatic HASH and LIST partition creation
Next
From: Robert Haas
Date:
Subject: Re: BUG #16419: wrong parsing BC year in to_date() function