aboutsummaryrefslogtreecommitdiff
path: root/contrib/btree_gist/btree_gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-04-26 19:46:26 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2019-04-26 19:46:37 -0400
commit7898d01da35772b16f6fa6d110ee8d2f8cc32af0 (patch)
treebc1f4da40fdb854f5a7e99d73efc83fa9cefe2ba /contrib/btree_gist/btree_gist.c
parentf6307bacabf555e9343fbf4f91723ce698303b03 (diff)
downloadpostgresql-7898d01da35772b16f6fa6d110ee8d2f8cc32af0.tar.gz
postgresql-7898d01da35772b16f6fa6d110ee8d2f8cc32af0.zip
Sync our copy of the timezone library with IANA release tzcode2019a.
This corrects a small bug in zic that caused it to output an incorrect year-2440 transition in the Africa/Casablanca zone. More interestingly, zic has grown a "-r" option that limits the range of zone transitions that it will put into the output files. That might be useful to people who don't like the weird GMT offsets that tzdb likes to use for very old dates. It appears that for dates before the cutoff time specified with -r, zic will use the zone's standard-time offset as of the cutoff time. So for example one might do make install ZIC_OPTIONS='-r @-1893456000' to cause all dates before 1910-01-01 to be treated as though 1910 standard time prevailed indefinitely far back. (Don't blame me for the unfriendly way of specifying the cutoff time --- it's seconds since or before the Unix epoch. You can use extract(epoch ...) to calculate it.) As usual, back-patch to all supported branches.
Diffstat (limited to 'contrib/btree_gist/btree_gist.c')
0 files changed, 0 insertions, 0 deletions