pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Fix CI failure introduced in commit 851f6649cc. 3+ messages / 1 participants [nested] [flat]
* pgsql: Fix CI failure introduced in commit 851f6649cc. @ 2026-01-29 03:33 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 3+ messages in thread From: Amit Kapila @ 2026-01-29 03:33 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix CI failure introduced in commit 851f6649cc. The test added in commit 851f6649cc uses a backup taken from a node created by the previous test to perform standby related checks. On Windows, however, the standby failed to start with the following error: FATAL: could not rename file "backup_label" to "backup_label.old": Permission denied This occurred because some background sessions from the earlier test were still active. These leftover processes continued accessing the parent directory of the backup_label file, likely preventing the rename and causing the failure. Ensuring that these sessions are cleanly terminated resolves the issue in local testing. Additionally, the has_restoring => 1 option has been removed, as it was not required by the new test. Reported-by: Robert Haas <robertmhaas@gmail.com> Backpatch-through: 17 Discussion: https://postgr.es/m/CA+TgmobdVhO0ckZfsBZ0wqDO4qHVCwZZx8sf=EinafvUam-dsQ@mail.gmail.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/3a98f989e8e596efb0db942ead90f64800136fac Modified Files -------------- src/test/recovery/t/046_checkpoint_logical_slot.pl | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 3+ messages in thread
* pgsql: Fix CI failure introduced in commit 851f6649cc. @ 2026-01-29 03:33 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 3+ messages in thread From: Amit Kapila @ 2026-01-29 03:33 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix CI failure introduced in commit 851f6649cc. The test added in commit 851f6649cc uses a backup taken from a node created by the previous test to perform standby related checks. On Windows, however, the standby failed to start with the following error: FATAL: could not rename file "backup_label" to "backup_label.old": Permission denied This occurred because some background sessions from the earlier test were still active. These leftover processes continued accessing the parent directory of the backup_label file, likely preventing the rename and causing the failure. Ensuring that these sessions are cleanly terminated resolves the issue in local testing. Additionally, the has_restoring => 1 option has been removed, as it was not required by the new test. Reported-by: Robert Haas <robertmhaas@gmail.com> Backpatch-through: 17 Discussion: https://postgr.es/m/CA+TgmobdVhO0ckZfsBZ0wqDO4qHVCwZZx8sf=EinafvUam-dsQ@mail.gmail.com Branch ------ REL_18_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/1c60f7236368ececfd9dc949251c28cebadfbe77 Modified Files -------------- src/test/recovery/t/046_checkpoint_logical_slot.pl | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 3+ messages in thread
* pgsql: Fix CI failure introduced in commit 851f6649cc. @ 2026-01-29 03:33 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 3+ messages in thread From: Amit Kapila @ 2026-01-29 03:33 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix CI failure introduced in commit 851f6649cc. The test added in commit 851f6649cc uses a backup taken from a node created by the previous test to perform standby related checks. On Windows, however, the standby failed to start with the following error: FATAL: could not rename file "backup_label" to "backup_label.old": Permission denied This occurred because some background sessions from the earlier test were still active. These leftover processes continued accessing the parent directory of the backup_label file, likely preventing the rename and causing the failure. Ensuring that these sessions are cleanly terminated resolves the issue in local testing. Additionally, the has_restoring => 1 option has been removed, as it was not required by the new test. Reported-by: Robert Haas <robertmhaas@gmail.com> Backpatch-through: 17 Discussion: https://postgr.es/m/CA+TgmobdVhO0ckZfsBZ0wqDO4qHVCwZZx8sf=EinafvUam-dsQ@mail.gmail.com Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/9649f1adfdee66a843cf97e0b292c489ba05e2ec Modified Files -------------- src/test/recovery/t/046_checkpoint_logical_slot.pl | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2026-01-29 03:33 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-01-29 03:33 pgsql: Fix CI failure introduced in commit 851f6649cc. Amit Kapila <akapila@postgresql.org> 2026-01-29 03:33 pgsql: Fix CI failure introduced in commit 851f6649cc. Amit Kapila <akapila@postgresql.org> 2026-01-29 03:33 pgsql: Fix CI failure introduced in commit 851f6649cc. Amit Kapila <akapila@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