pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Test restartpoints in archive recovery. 6+ messages / 1 participants [nested] [flat]
* pgsql: Test restartpoints in archive recovery. @ 2025-04-20 15:30 Noah Misch <noah@leadboat.com> 0 siblings, 0 replies; 6+ messages in thread From: Noah Misch @ 2025-04-20 15:30 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Test restartpoints in archive recovery. v14 commit 1f95181b44c843729caaa688f74babe9403b5850 and its v13 equivalent caused timing-dependent failures in archive recovery, at restartpoints. The symptom was "invalid magic number 0000 in log segment X, offset 0", "unexpected pageaddr X in log segment Y, offset 0" [X < Y], or an assertion failure. Commit 3635a0a35aafd3bfa80b7a809bc6e91ccd36606a and predecessors back-patched v15 changes to fix that. This test reproduces the problem probabilistically, typically in less than 1000 iterations of the test. Hence, buildfarm and CI runs would have surfaced enough failures to get attention within a day. Reported-by: Arun Thirupathi <arunth@google.com> Discussion: https://postgr.es/m/20250306193013.36.nmisch@google.com Backpatch-through: 13 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/714bd9e3a733a98da47531a750182ee5981cc3ed Modified Files -------------- src/test/recovery/meson.build | 1 + src/test/recovery/t/045_archive_restartpoint.pl | 57 +++++++++++++++++++++++++ 2 files changed, 58 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Test restartpoints in archive recovery. @ 2025-04-20 15:30 Noah Misch <noah@leadboat.com> 0 siblings, 0 replies; 6+ messages in thread From: Noah Misch @ 2025-04-20 15:30 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Test restartpoints in archive recovery. v14 commit 1f95181b44c843729caaa688f74babe9403b5850 and its v13 equivalent caused timing-dependent failures in archive recovery, at restartpoints. The symptom was "invalid magic number 0000 in log segment X, offset 0", "unexpected pageaddr X in log segment Y, offset 0" [X < Y], or an assertion failure. Commit 3635a0a35aafd3bfa80b7a809bc6e91ccd36606a and predecessors back-patched v15 changes to fix that. This test reproduces the problem probabilistically, typically in less than 1000 iterations of the test. Hence, buildfarm and CI runs would have surfaced enough failures to get attention within a day. Reported-by: Arun Thirupathi <arunth@google.com> Discussion: https://postgr.es/m/20250306193013.36.nmisch@google.com Backpatch-through: 13 Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/e297ddcfb7d37f54567b9a9bb87ef15e0aedc0d5 Modified Files -------------- src/test/recovery/meson.build | 1 + src/test/recovery/t/045_archive_restartpoint.pl | 57 +++++++++++++++++++++++++ 2 files changed, 58 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Test restartpoints in archive recovery. @ 2025-04-20 15:30 Noah Misch <noah@leadboat.com> 0 siblings, 0 replies; 6+ messages in thread From: Noah Misch @ 2025-04-20 15:30 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Test restartpoints in archive recovery. v14 commit 1f95181b44c843729caaa688f74babe9403b5850 and its v13 equivalent caused timing-dependent failures in archive recovery, at restartpoints. The symptom was "invalid magic number 0000 in log segment X, offset 0", "unexpected pageaddr X in log segment Y, offset 0" [X < Y], or an assertion failure. Commit 3635a0a35aafd3bfa80b7a809bc6e91ccd36606a and predecessors back-patched v15 changes to fix that. This test reproduces the problem probabilistically, typically in less than 1000 iterations of the test. Hence, buildfarm and CI runs would have surfaced enough failures to get attention within a day. Reported-by: Arun Thirupathi <arunth@google.com> Discussion: https://postgr.es/m/20250306193013.36.nmisch@google.com Backpatch-through: 13 Branch ------ REL_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/4664de1826a8b24baa96502121dcfcccbef06e72 Modified Files -------------- src/test/recovery/meson.build | 1 + src/test/recovery/t/045_archive_restartpoint.pl | 57 +++++++++++++++++++++++++ 2 files changed, 58 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Test restartpoints in archive recovery. @ 2025-04-20 15:30 Noah Misch <noah@leadboat.com> 0 siblings, 0 replies; 6+ messages in thread From: Noah Misch @ 2025-04-20 15:30 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Test restartpoints in archive recovery. v14 commit 1f95181b44c843729caaa688f74babe9403b5850 and its v13 equivalent caused timing-dependent failures in archive recovery, at restartpoints. The symptom was "invalid magic number 0000 in log segment X, offset 0", "unexpected pageaddr X in log segment Y, offset 0" [X < Y], or an assertion failure. Commit 3635a0a35aafd3bfa80b7a809bc6e91ccd36606a and predecessors back-patched v15 changes to fix that. This test reproduces the problem probabilistically, typically in less than 1000 iterations of the test. Hence, buildfarm and CI runs would have surfaced enough failures to get attention within a day. Reported-by: Arun Thirupathi <arunth@google.com> Discussion: https://postgr.es/m/20250306193013.36.nmisch@google.com Backpatch-through: 13 Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/91168a9ae38dc986a690fcb7ca5c28cf0036199a Modified Files -------------- src/test/recovery/t/045_archive_restartpoint.pl | 57 +++++++++++++++++++++++++ 1 file changed, 57 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Test restartpoints in archive recovery. @ 2025-04-20 15:30 Noah Misch <noah@leadboat.com> 0 siblings, 0 replies; 6+ messages in thread From: Noah Misch @ 2025-04-20 15:30 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Test restartpoints in archive recovery. v14 commit 1f95181b44c843729caaa688f74babe9403b5850 and its v13 equivalent caused timing-dependent failures in archive recovery, at restartpoints. The symptom was "invalid magic number 0000 in log segment X, offset 0", "unexpected pageaddr X in log segment Y, offset 0" [X < Y], or an assertion failure. Commit 3635a0a35aafd3bfa80b7a809bc6e91ccd36606a and predecessors back-patched v15 changes to fix that. This test reproduces the problem probabilistically, typically in less than 1000 iterations of the test. Hence, buildfarm and CI runs would have surfaced enough failures to get attention within a day. Reported-by: Arun Thirupathi <arunth@google.com> Discussion: https://postgr.es/m/20250306193013.36.nmisch@google.com Backpatch-through: 13 Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/41ffd9d6a72486efb182c4f937866cf6e069a8ec Modified Files -------------- src/test/recovery/t/045_archive_restartpoint.pl | 57 +++++++++++++++++++++++++ 1 file changed, 57 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Test restartpoints in archive recovery. @ 2025-04-20 15:30 Noah Misch <noah@leadboat.com> 0 siblings, 0 replies; 6+ messages in thread From: Noah Misch @ 2025-04-20 15:30 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Test restartpoints in archive recovery. v14 commit 1f95181b44c843729caaa688f74babe9403b5850 and its v13 equivalent caused timing-dependent failures in archive recovery, at restartpoints. The symptom was "invalid magic number 0000 in log segment X, offset 0", "unexpected pageaddr X in log segment Y, offset 0" [X < Y], or an assertion failure. Commit 3635a0a35aafd3bfa80b7a809bc6e91ccd36606a and predecessors back-patched v15 changes to fix that. This test reproduces the problem probabilistically, typically in less than 1000 iterations of the test. Hence, buildfarm and CI runs would have surfaced enough failures to get attention within a day. Reported-by: Arun Thirupathi <arunth@google.com> Discussion: https://postgr.es/m/20250306193013.36.nmisch@google.com Backpatch-through: 13 Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/4399d1055627fe5ffaba47cf6ad6d07af3905e16 Modified Files -------------- src/test/recovery/t/045_archive_restartpoint.pl | 57 +++++++++++++++++++++++++ 1 file changed, 57 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2025-04-20 15:30 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-04-20 15:30 pgsql: Test restartpoints in archive recovery. Noah Misch <noah@leadboat.com> 2025-04-20 15:30 pgsql: Test restartpoints in archive recovery. Noah Misch <noah@leadboat.com> 2025-04-20 15:30 pgsql: Test restartpoints in archive recovery. Noah Misch <noah@leadboat.com> 2025-04-20 15:30 pgsql: Test restartpoints in archive recovery. Noah Misch <noah@leadboat.com> 2025-04-20 15:30 pgsql: Test restartpoints in archive recovery. Noah Misch <noah@leadboat.com> 2025-04-20 15:30 pgsql: Test restartpoints in archive recovery. Noah Misch <noah@leadboat.com>
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