pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Stabilize the FORCE drop test for online data checksums 2+ messages / 1 participants [nested] [flat]
* pgsql: Stabilize the FORCE drop test for online data checksums @ 2026-08-18 20:40 Daniel Gustafsson <dgustafsson@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Daniel Gustafsson @ 2026-08-18 20:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Stabilize the FORCE drop test for online data checksums Commit 51f55b13a4d added a test where DROP DATABASE ... WITH (FORCE) terminates a session holding a temporary table in the target database. While exiting, the terminated session drops its temporary table and commits, and the commit waits for a WAL flush behind the backlog generated by the checksum workers. On machines with slow storage this can exceed the five seconds DROP DATABASE waits for terminated backends to exit, making the test fail with "database "dropmeforce" is being accessed by other users", as observed on buildfarm member turaco. To fix, use asynchronous commit in the terminated session, so that its exit does not wait for a WAL flush, and checkpoint before the drop so that the exit-time WAL records do not queue up behind the backlog. Author: Zsolt Parragi <zsolt.parragi@percona.com> Reported-by: Alexander Lakhin <exclusion@gmail.com> Discussion: https://postgr.es/m/361531e2-52b5-499c-a126-815f277bbef2@gmail.com Backpatch-through: 19 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/f7a0cca2e35e36cb08817a40650a086d982ed942 Modified Files -------------- src/test/modules/test_checksums/t/001_basic.pl | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Stabilize the FORCE drop test for online data checksums @ 2026-08-18 20:41 Daniel Gustafsson <dgustafsson@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Daniel Gustafsson @ 2026-08-18 20:41 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Stabilize the FORCE drop test for online data checksums Commit 51f55b13a4d added a test where DROP DATABASE ... WITH (FORCE) terminates a session holding a temporary table in the target database. While exiting, the terminated session drops its temporary table and commits, and the commit waits for a WAL flush behind the backlog generated by the checksum workers. On machines with slow storage this can exceed the five seconds DROP DATABASE waits for terminated backends to exit, making the test fail with "database "dropmeforce" is being accessed by other users", as observed on buildfarm member turaco. To fix, use asynchronous commit in the terminated session, so that its exit does not wait for a WAL flush, and checkpoint before the drop so that the exit-time WAL records do not queue up behind the backlog. Author: Zsolt Parragi <zsolt.parragi@percona.com> Reported-by: Alexander Lakhin <exclusion@gmail.com> Discussion: https://postgr.es/m/361531e2-52b5-499c-a126-815f277bbef2@gmail.com Backpatch-through: 19 Branch ------ REL_19_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/1d28812160d4e7ec06ebb2223d2c67b0dec74720 Modified Files -------------- src/test/modules/test_checksums/t/001_basic.pl | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2026-08-18 20:41 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-08-18 20:40 pgsql: Stabilize the FORCE drop test for online data checksums Daniel Gustafsson <dgustafsson@postgresql.org> 2026-08-18 20:41 pgsql: Stabilize the FORCE drop test for online data checksums Daniel Gustafsson <dgustafsson@postgresql.org>
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