pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: BUG #16419: wrong parsing BC year in to_date() function
Date: Wed, 30 Sep 2020 17:35:43 -0400
Message-ID: <911841.1601501743@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+TgmoameT7ysPOm2sqp6NaZtzP0QFNjJ09wC1QVKTzt-84D7Q@mail.gmail.com>
References: <16419-d8d9db0a7553f01b@postgresql.org>
	<CAKFQuwYPjq=UAHNZ6KtHuJPA8pmttV3X+imFYcBQqNUGWsCexg@mail.gmail.com>
	<AM0PR03MB3570F99911704BFC77294DA1BFA50@AM0PR03MB3570.eurprd03.prod.outlook.com>
	<CAKFQuwaXESne_VYt8bE8L5gGGqEM0TCGL+JNL1a8NJ2_uc8VfQ@mail.gmail.com>
	<CAKFQuwajC7+s-nHRujP+w5GsUTcp8usazdPas59Kz3kCTq+e3w@mail.gmail.com>
	<0123b852ae3fe53eca11b9451d035411b06dafd5.camel@cybertec.at>
	<CAKFQuwb_3yNTTE6cG_YtXFtV=CkQf0uMSMB0oxC1YNrF94pfuA@mail.gmail.com>
	<20200904012149.GA13932@momjian.us>
	<CAKFQuwZV0UxbyYTxuJhf1j1X=3HG5QA6qtEp+C+=LzOFtNEt3A@mail.gmail.com>
	<20200904201224.GD6891@momjian.us>
	<663099.1601400389@sss.pgh.pa.us>
	<CA+TgmoameT7ysPOm2sqp6NaZtzP0QFNjJ09wC1QVKTzt-84D7Q@mail.gmail.com>

Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Sep 29, 2020 at 1:26 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I think this is nuts.  The current behavior is obviously broken;
>> we should just treat it as a bug and fix it, including back-patching.
>> I do not think there is a compatibility problem of any significance.
>> Who out there is going to have an application that is relying on the
>> ability to insert BC dates in this way?

> I think that's entirely the wrong way to look at it. If nobody is
> using the feature, then it will not break anything to change the
> behavior, but on the other hand there is no reason to fix the bug
> either. But if people are using the feature, making it behave
> differently in the next minor release is going to break their
> applications. I disagree *strongly* with making such changes in stable
> branches and feel that the change to those branches should be
> reverted.

By that logic, we should never fix any bug in a back branch.

			regards, tom lane





view thread (31+ messages)  latest in thread

Message-ID: <911841.1601501743@sss.pgh.pa.us>
Permalink:  ../911841.1601501743@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/911841.1601501743@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, robertmhaas@gmail.com, bruce@momjian.us, david.g.johnston@gmail.com, laurenz.albe@cybertec.at, pgsql-hackers@lists.postgresql.org
  Subject: Re: BUG #16419: wrong parsing BC year in to_date() function
  In-Reply-To: <911841.1601501743@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox