Horton

Re: BUG #16419: wrong parsing BC year in to_date() function

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, Laurenz Albe <laurenz.albe@cybertec.at>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-09-30T18:50:31Z
Lists: pgsql-bugs, pgsql-hackers 
Bruce Momjian <bruce@momjian.us> writes:
> On Wed, Sep 30, 2020 at 02:11:54PM -0400, Tom Lane wrote:
>> Hm, I read your reference to "the release notes" as suggesting that
>> we should change it only in a major release, ie HEAD only (and it
>> looks like David read it the same).  If you meant minor release notes,
>> then we're on the same page.

> Yes, I was thinking just the major release notes.  What are you
> suggesting, and what did you ultimately decide to do?  What I didn't
> want to do was to document the old behavior in the old docs and change
> it in PG 14.

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.

			regards, tom lane

Commits

  1. Fix handling of BC years in to_date/to_timestamp.

  2. Fix make_timestamp[tz] to accept negative years as meaning BC.

  3. doc: PG 13 relnotes, update TOAST item to mention decompression