| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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-09-29 17:50:07 |
| Message-ID: | 686732.1601401807@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> Adding support for negative years in make_timestamp seems pretty
> straightforward; see attached patch.
In hopes of moving things along, I pushed that, along with documentation
additions. I couldn't quite convince myself that it was a bug fix
though, so no back-patch. (I don't think we really need any doc
changes about it in the back branches, either.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nagaraj Raj | 2020-09-29 18:18:25 | Re: table partition with inheritance having current_timestamp issue if we miss range table |
| Previous Message | PG Bug reporting form | 2020-09-29 17:31:48 | BUG #16642: INFORMATION_SCHEMA-DESIGN |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey M. Borodin | 2020-09-29 18:04:18 | Re: Yet another fast GiST build |
| Previous Message | Tom Lane | 2020-09-29 17:26:29 | Re: BUG #16419: wrong parsing BC year in to_date() function |