summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-09-30 15:40:23 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-09-30 15:40:23 -0400
commit489c9c3407cbfd473c2f8d7863ffaaf6d2e8fcf8 (patch)
tree2f94b3774a89425af70bb3df17e9629b37de75e3 /src/backend/access/gist/gistbuild.c
parent9796f455c38e9e79847443529ff2166b1a6f714f (diff)
downloadpostgresql-489c9c3407cbfd473c2f8d7863ffaaf6d2e8fcf8.tar.gz
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/gistbuild.c')
0 files changed, 0 insertions, 0 deletions