| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, 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-10-01 00:38:05 |
| Message-ID: | CAKFQuwZEtZfc7npBFEhDNpiv_ShvaVW-GQ7RhzZOD9c+viNTeA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Sep 30, 2020 at 5:24 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> The
> fact that we've suddenly discovered that this is not what Oracle does
> doesn't mean that no users have discovered that it is what PostgreSQL
> does.
>
Presently I cannot seem to make up my mind so I'm going to go with my
original opinion which was to only change the behavior in v14. In part
because it seems appropriate given our generally laissez-faire attitude
toward this particular feature.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-10-01 00:40:58 | Re: BUG #16419: wrong parsing BC year in to_date() function |
| Previous Message | Robert Haas | 2020-10-01 00:24:30 | Re: BUG #16419: wrong parsing BC year in to_date() function |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-10-01 00:40:58 | Re: BUG #16419: wrong parsing BC year in to_date() function |
| Previous Message | Robert Haas | 2020-10-01 00:24:30 | Re: BUG #16419: wrong parsing BC year in to_date() function |