pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. 6+ messages / 1 participants [nested] [flat]
* pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. @ 2021-09-06 15:30 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2021-09-06 15:30 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/599c73a91a0471465a84f12fe6a2e7236a825721 Modified Files -------------- src/backend/utils/adt/date.c | 2 ++ 1 file changed, 2 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. @ 2021-09-06 15:30 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2021-09-06 15:30 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/d8a266c5e1bd50785d4619ecb3e686f86771685f Modified Files -------------- src/backend/utils/adt/date.c | 2 ++ 1 file changed, 2 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. @ 2021-09-06 15:30 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2021-09-06 15:30 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/eb3c8d24808a4d3ee8a257f4b856d5583b5cfdaa Modified Files -------------- src/backend/utils/adt/date.c | 2 ++ 1 file changed, 2 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. @ 2021-09-06 15:30 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2021-09-06 15:30 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/90b4647f63dae68181557d244717a7615831243d Modified Files -------------- src/backend/utils/adt/date.c | 2 ++ 1 file changed, 2 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. @ 2021-09-06 15:30 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2021-09-06 15:30 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/b28c862a6c11c5f9fc77687124747d551b7c74a1 Modified Files -------------- src/backend/utils/adt/date.c | 2 ++ 1 file changed, 2 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. @ 2021-09-06 15:30 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2021-09-06 15:30 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL9_6_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/5907c3818c43a1e0b946acc09df6dcbba42f621f Modified Files -------------- src/backend/utils/adt/date.c | 2 ++ 1 file changed, 2 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2021-09-06 15:30 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2021-09-06 15:30 pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. Tom Lane <tgl@sss.pgh.pa.us> 2021-09-06 15:30 pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. Tom Lane <tgl@sss.pgh.pa.us> 2021-09-06 15:30 pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. Tom Lane <tgl@sss.pgh.pa.us> 2021-09-06 15:30 pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. Tom Lane <tgl@sss.pgh.pa.us> 2021-09-06 15:30 pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. Tom Lane <tgl@sss.pgh.pa.us> 2021-09-06 15:30 pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox