diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-09-30 15:40:23 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-09-30 15:40:23 -0400 |
| commit | c5232dca8d1bbe1cab4a2d6773566ff53146340b (patch) | |
| tree | d938f0fa29b0aedfecba7f7bea7b4fc6d85cee62 /src/backend/access/gist/gistget.c | |
| parent | 5c7afb4a29aa0f75def751406b4004e7f047a7f3 (diff) | |
| download | postgresql-c5232dca8d1bbe1cab4a2d6773566ff53146340b.tar.gz postgresql-c5232dca8d1bbe1cab4a2d6773566ff53146340b.zip | |
Fix handling of BC years in to_date/to_timestamp.
Previously, a conversion such as
to_date('-44-02-01','YYYY-MM-DD')
would result in '0045-02-01 BC', as the code attempted to interpret
the negative year as BC, but failed to apply the correction needed
for our internal handling of BC years. Fix the off-by-one problem.
Also, arrange for the combination of a negative year and an
explicit "BC" marker to cancel out and produce AD. This is how
the negative-century case works, so it seems sane to do likewise.
Continue to read "year 0000" as 1 BC. Oracle would throw an error,
but we've accepted that case for a long time so I'm hesitant to
change it in a back-patch.
Per bug #16419 from Saeed Hubaishan. Back-patch to all supported
branches.
Dar Alathar-Yemen and Tom Lane
Discussion: https://postgr.es/m/16419-d8d9db0a7553f01b@postgresql.org
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions