aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-09-06 11:29:52 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-09-06 11:29:52 -0400
commitd8a266c5e1bd50785d4619ecb3e686f86771685f (patch)
tree75fad0541cdb02686d83e062407bc75cee775854 /src
parent9f9ae019d194d012c74084cec3722ba2d67af8eb (diff)
downloadpostgresql-d8a266c5e1bd50785d4619ecb3e686f86771685f.tar.gz
postgresql-d8a266c5e1bd50785d4619ecb3e686f86771685f.zip
Fix bogus timetz_zone() results for DYNTZ abbreviations.
timetz_zone() delivered completely wrong answers if the zone was specified by a dynamic TZ abbreviation, because it failed to account for the difference between the POSIX conventions for field values in struct pg_tm and the conventions used in PG-specific datetime code. As a stopgap fix, just adjust the tm_year and tm_mon fields to match PG conventions. This is fixed in a different way in HEAD (388e71af8) but I don't want to back-patch the change of reference point. Discussion: https://postgr.es/m/CAJ7c6TOMG8zSNEZtCn5SPe+cCk3Lfxb71ZaQwT2F4T7PJ_t=KA@mail.gmail.com
Diffstat (limited to 'src')
-rw-r--r--src/backend/utils/adt/date.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/backend/utils/adt/date.c b/src/backend/utils/adt/date.c
index 4c48ff455ce..e798c1a78ee 100644
--- a/src/backend/utils/adt/date.c
+++ b/src/backend/utils/adt/date.c
@@ -2832,6 +2832,8 @@ timetz_zone(PG_FUNCTION_ARGS)
struct pg_tm *tm;
tm = pg_localtime(&now, tzp);
+ tm->tm_year += 1900; /* adjust to PG conventions */
+ tm->tm_mon += 1;
tz = DetermineTimeZoneAbbrevOffset(tm, tzname, tzp);
}
else