pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Drop global objects after completed test 6+ messages / 2 participants [nested] [flat]
* pgsql: Drop global objects after completed test @ 2024-04-03 11:41 Daniel Gustafsson <dgustafsson@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Daniel Gustafsson @ 2024-04-03 11:41 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Drop global objects after completed test Project policy is to not leave global objects behind after a regress test run. This was found as a result of the development of a patch to make pg_regress detect such leftovers automatically, which in the end was withdrawn due to issues with parallel runs. Discussion: https://postgr.es/m/E1phvk7-000VAH-7k@gemulon.postgresql.org Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/936e3fa3787a51397280c1081587586e83c20399 Modified Files -------------- src/test/modules/test_pg_dump/expected/test_pg_dump.out | 2 ++ src/test/modules/test_pg_dump/sql/test_pg_dump.sql | 3 +++ 2 files changed, 5 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Drop global objects after completed test @ 2024-09-24 03:12 Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 6+ messages in thread From: Michael Paquier @ 2024-09-24 03:12 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Drop global objects after completed test Project policy is to not leave global objects behind after a regress test run. This was found as a result of the development of a patch to make pg_regress detect such leftovers automatically, which in the end was withdrawn due to issues with parallel runs. This was originally committed as 936e3fa3787a, but the issue also exists in the 12~16 range. Discussion: https://postgr.es/m/E1phvk7-000VAH-7k@gemulon.postgresql.org Backpatch-through: 12 Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/e43e71b6cd2f440e84da8a4a245837afba28b84f Author: Daniel Gustafsson <dgustafsson@postgresql.org> Modified Files -------------- src/test/modules/test_pg_dump/expected/test_pg_dump.out | 2 ++ src/test/modules/test_pg_dump/sql/test_pg_dump.sql | 4 ++++ 2 files changed, 6 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Drop global objects after completed test @ 2024-09-24 03:12 Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 6+ messages in thread From: Michael Paquier @ 2024-09-24 03:12 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Drop global objects after completed test Project policy is to not leave global objects behind after a regress test run. This was found as a result of the development of a patch to make pg_regress detect such leftovers automatically, which in the end was withdrawn due to issues with parallel runs. This was originally committed as 936e3fa3787a, but the issue also exists in the 12~16 range. Discussion: https://postgr.es/m/E1phvk7-000VAH-7k@gemulon.postgresql.org Backpatch-through: 12 Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/2eecaf4b8cfb495a77512b7123f2867319973d29 Author: Daniel Gustafsson <dgustafsson@postgresql.org> Modified Files -------------- src/test/modules/test_pg_dump/expected/test_pg_dump.out | 2 ++ src/test/modules/test_pg_dump/sql/test_pg_dump.sql | 4 ++++ 2 files changed, 6 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Drop global objects after completed test @ 2024-09-24 03:12 Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 6+ messages in thread From: Michael Paquier @ 2024-09-24 03:12 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Drop global objects after completed test Project policy is to not leave global objects behind after a regress test run. This was found as a result of the development of a patch to make pg_regress detect such leftovers automatically, which in the end was withdrawn due to issues with parallel runs. This was originally committed as 936e3fa3787a, but the issue also exists in the 12~16 range. Discussion: https://postgr.es/m/E1phvk7-000VAH-7k@gemulon.postgresql.org Backpatch-through: 12 Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/988ddbef978bb2f247f0e021a28527e3776d6906 Author: Daniel Gustafsson <dgustafsson@postgresql.org> Modified Files -------------- src/test/modules/test_pg_dump/expected/test_pg_dump.out | 2 ++ src/test/modules/test_pg_dump/sql/test_pg_dump.sql | 4 ++++ 2 files changed, 6 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Drop global objects after completed test @ 2024-09-24 03:12 Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 6+ messages in thread From: Michael Paquier @ 2024-09-24 03:12 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Drop global objects after completed test Project policy is to not leave global objects behind after a regress test run. This was found as a result of the development of a patch to make pg_regress detect such leftovers automatically, which in the end was withdrawn due to issues with parallel runs. This was originally committed as 936e3fa3787a, but the issue also exists in the 12~16 range. Discussion: https://postgr.es/m/E1phvk7-000VAH-7k@gemulon.postgresql.org Backpatch-through: 12 Branch ------ REL_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/4dd17490faa34c2dc4725593f7866c3f18f76e7d Author: Daniel Gustafsson <dgustafsson@postgresql.org> Modified Files -------------- src/test/modules/test_pg_dump/expected/test_pg_dump.out | 2 ++ src/test/modules/test_pg_dump/sql/test_pg_dump.sql | 4 ++++ 2 files changed, 6 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Drop global objects after completed test @ 2024-09-24 03:12 Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 6+ messages in thread From: Michael Paquier @ 2024-09-24 03:12 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Drop global objects after completed test Project policy is to not leave global objects behind after a regress test run. This was found as a result of the development of a patch to make pg_regress detect such leftovers automatically, which in the end was withdrawn due to issues with parallel runs. This was originally committed as 936e3fa3787a, but the issue also exists in the 12~16 range. Discussion: https://postgr.es/m/E1phvk7-000VAH-7k@gemulon.postgresql.org Backpatch-through: 12 Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/8ec99d0b79b236c14660ff2f3beb6ee9747e8f5c Author: Daniel Gustafsson <dgustafsson@postgresql.org> Modified Files -------------- src/test/modules/test_pg_dump/expected/test_pg_dump.out | 2 ++ src/test/modules/test_pg_dump/sql/test_pg_dump.sql | 4 ++++ 2 files changed, 6 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2024-09-24 03:12 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-04-03 11:41 pgsql: Drop global objects after completed test Daniel Gustafsson <dgustafsson@postgresql.org> 2024-09-24 03:12 pgsql: Drop global objects after completed test Michael Paquier <michael@paquier.xyz> 2024-09-24 03:12 pgsql: Drop global objects after completed test Michael Paquier <michael@paquier.xyz> 2024-09-24 03:12 pgsql: Drop global objects after completed test Michael Paquier <michael@paquier.xyz> 2024-09-24 03:12 pgsql: Drop global objects after completed test Michael Paquier <michael@paquier.xyz> 2024-09-24 03:12 pgsql: Drop global objects after completed test Michael Paquier <michael@paquier.xyz>
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