Re: Prevent premature startup of pg_upgrade targets

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Nikolay Samokhvalov <nik(at)postgres(dot)ai>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Prevent premature startup of pg_upgrade targets
Date: 2026-08-14 18:57:36
Message-ID: 42D6E812-B4C6-4DA1-8428-D58A21E16B05@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 14 Aug 2026, at 07:31, Nikolay Samokhvalov <nik(at)postgres(dot)ai> wrote:

> There is already narrower protection for the old cluster. In link and
> swap modes, disable_old_cluster() renames pg_control before file
> transfer. The target has no equivalent protection.

Sounds like a reasonable idea to add a layer of protection to the new cluster
as well, to prevent accidental startups.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-08-14 19:01:19 Re: CREATE OR REPLACE MATERIALIZED VIEW
Previous Message Nathan Bossart 2026-08-14 18:42:26 Re: missing PGDLLIMPORT in utils/acl.h after CVE-related "Invalidate plan cache after role changes"