pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Back-patch test cases for timetz_zone/timetz_izone. 6+ messages / 1 participants [nested] [flat]
* pgsql: Back-patch test cases for timetz_zone/timetz_izone. @ 2023-10-17 17:56 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2023-10-17 17:56 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Back-patch test cases for timetz_zone/timetz_izone. Per code coverage reports, we had zero regression test coverage of these functions. That came back to bite us, as apparently that's allowed us to miss discovering misbehavior of this code with AIX's xlc compiler. Install relevant portions of the test cases added in 97957fdba, 2f0472030, 19fa97731. (Assuming the expected outcome that the xlc problem does appear in back branches, a code fix will follow.) Discussion: https://postgr.es/m/CA+hUKGK=DOC+hE-62FKfZy=Ybt5uLkrg3zCZD-jFykM-iPn8yw@mail.gmail.com Branch ------ REL_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/4a427b82cf19f1b05ca9e26704f8f924af758ded Modified Files -------------- src/test/regress/expected/timetz.out | 60 ++++++++++++++++++++++++++++++++++++ src/test/regress/sql/timetz.sql | 20 ++++++++++++ 2 files changed, 80 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Back-patch test cases for timetz_zone/timetz_izone. @ 2023-10-17 17:56 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2023-10-17 17:56 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Back-patch test cases for timetz_zone/timetz_izone. Per code coverage reports, we had zero regression test coverage of these functions. That came back to bite us, as apparently that's allowed us to miss discovering misbehavior of this code with AIX's xlc compiler. Install relevant portions of the test cases added in 97957fdba, 2f0472030, 19fa97731. (Assuming the expected outcome that the xlc problem does appear in back branches, a code fix will follow.) Discussion: https://postgr.es/m/CA+hUKGK=DOC+hE-62FKfZy=Ybt5uLkrg3zCZD-jFykM-iPn8yw@mail.gmail.com Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/b18781c2df44c2abf18dca95b1351ff917caf5fb Modified Files -------------- src/test/regress/expected/timetz.out | 60 ++++++++++++++++++++++++++++++++++++ src/test/regress/sql/timetz.sql | 20 ++++++++++++ 2 files changed, 80 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Back-patch test cases for timetz_zone/timetz_izone. @ 2023-10-17 17:56 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2023-10-17 17:56 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Back-patch test cases for timetz_zone/timetz_izone. Per code coverage reports, we had zero regression test coverage of these functions. That came back to bite us, as apparently that's allowed us to miss discovering misbehavior of this code with AIX's xlc compiler. Install relevant portions of the test cases added in 97957fdba, 2f0472030, 19fa97731. (Assuming the expected outcome that the xlc problem does appear in back branches, a code fix will follow.) Discussion: https://postgr.es/m/CA+hUKGK=DOC+hE-62FKfZy=Ybt5uLkrg3zCZD-jFykM-iPn8yw@mail.gmail.com Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/29231dbd40cbebe7651ca718d084b5b5ed3a9f00 Modified Files -------------- src/test/regress/expected/timetz.out | 60 ++++++++++++++++++++++++++++++++++++ src/test/regress/sql/timetz.sql | 20 ++++++++++++ 2 files changed, 80 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Back-patch test cases for timetz_zone/timetz_izone. @ 2023-10-17 17:56 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2023-10-17 17:56 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Back-patch test cases for timetz_zone/timetz_izone. Per code coverage reports, we had zero regression test coverage of these functions. That came back to bite us, as apparently that's allowed us to miss discovering misbehavior of this code with AIX's xlc compiler. Install relevant portions of the test cases added in 97957fdba, 2f0472030, 19fa97731. (Assuming the expected outcome that the xlc problem does appear in back branches, a code fix will follow.) Discussion: https://postgr.es/m/CA+hUKGK=DOC+hE-62FKfZy=Ybt5uLkrg3zCZD-jFykM-iPn8yw@mail.gmail.com Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/05b4614decacbe84fb3fde0d9266fe66f525a7e7 Modified Files -------------- src/test/regress/expected/timetz.out | 60 ++++++++++++++++++++++++++++++++++++ src/test/regress/sql/timetz.sql | 20 ++++++++++++ 2 files changed, 80 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Back-patch test cases for timetz_zone/timetz_izone. @ 2023-10-17 17:56 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2023-10-17 17:56 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Back-patch test cases for timetz_zone/timetz_izone. Per code coverage reports, we had zero regression test coverage of these functions. That came back to bite us, as apparently that's allowed us to miss discovering misbehavior of this code with AIX's xlc compiler. Install relevant portions of the test cases added in 97957fdba, 2f0472030, 19fa97731. (Assuming the expected outcome that the xlc problem does appear in back branches, a code fix will follow.) Discussion: https://postgr.es/m/CA+hUKGK=DOC+hE-62FKfZy=Ybt5uLkrg3zCZD-jFykM-iPn8yw@mail.gmail.com Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/dc159b95d921e12e82820301413945eff1ca88b0 Modified Files -------------- src/test/regress/expected/timetz.out | 60 ++++++++++++++++++++++++++++++++++++ src/test/regress/sql/timetz.sql | 20 ++++++++++++ 2 files changed, 80 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Back-patch test cases for timetz_zone/timetz_izone. @ 2023-10-17 17:56 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2023-10-17 17:56 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Back-patch test cases for timetz_zone/timetz_izone. Per code coverage reports, we had zero regression test coverage of these functions. That came back to bite us, as apparently that's allowed us to miss discovering misbehavior of this code with AIX's xlc compiler. Install relevant portions of the test cases added in 97957fdba, 2f0472030, 19fa97731. (Assuming the expected outcome that the xlc problem does appear in back branches, a code fix will follow.) Discussion: https://postgr.es/m/CA+hUKGK=DOC+hE-62FKfZy=Ybt5uLkrg3zCZD-jFykM-iPn8yw@mail.gmail.com Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/fdf8b70a51cfdde5194b457f985dc16545c73d78 Modified Files -------------- src/test/regress/expected/timetz.out | 60 ++++++++++++++++++++++++++++++++++++ src/test/regress/sql/timetz.sql | 20 ++++++++++++ 2 files changed, 80 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2023-10-17 17:56 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2023-10-17 17:56 pgsql: Back-patch test cases for timetz_zone/timetz_izone. Tom Lane <tgl@sss.pgh.pa.us> 2023-10-17 17:56 pgsql: Back-patch test cases for timetz_zone/timetz_izone. Tom Lane <tgl@sss.pgh.pa.us> 2023-10-17 17:56 pgsql: Back-patch test cases for timetz_zone/timetz_izone. Tom Lane <tgl@sss.pgh.pa.us> 2023-10-17 17:56 pgsql: Back-patch test cases for timetz_zone/timetz_izone. Tom Lane <tgl@sss.pgh.pa.us> 2023-10-17 17:56 pgsql: Back-patch test cases for timetz_zone/timetz_izone. Tom Lane <tgl@sss.pgh.pa.us> 2023-10-17 17:56 pgsql: Back-patch test cases for timetz_zone/timetz_izone. 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