aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvalidate.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-10-29 15:28:14 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-10-29 15:28:14 -0400
commit4a071afbd056282746a5bc9362e87f579a56402d (patch)
treef9003b46921a14a67b89aff741f9d1a2d8c1bf79 /src/backend/access/gist/gistvalidate.c
parentf90149e6285aaae6b48559afce1bd638ee26c33e (diff)
downloadpostgresql-4a071afbd056282746a5bc9362e87f579a56402d.tar.gz
postgresql-4a071afbd056282746a5bc9362e87f579a56402d.zip
Stabilize timetz test across DST transitions.
The timetz test cases I added in commit a9632830b were unintentionally sensitive to whether or not DST is active in the PST8PDT time zone. Thus, they'll start failing this coming weekend, as reported by Bernhard M. Wiedemann in bug #16689. Fortunately, DST-awareness is not significant to the purpose of these test cases, so we can just force them all to PDT (DST hours) to preserve stability of the results. Back-patch to v10, as the prior patch was. Discussion: https://postgr.es/m/16689-57701daa23b377bf@postgresql.org
Diffstat (limited to 'src/backend/access/gist/gistvalidate.c')
0 files changed, 0 insertions, 0 deletions