Re: BUG #19908: pg_upgrade --check crashes instance if running in a different PID Namespace then the old cluster

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: schefner20(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19908: pg_upgrade --check crashes instance if running in a different PID Namespace then the old cluster
Date: 2026-11-16 21:36:55
Message-ID: CA+TgmoaTDJBjGx7HQBJyCOP3jg=dy--U9ohjF=VUneKPdTrhNQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Nov 16, 2026 at 3:40 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Moreover, I think making it safe or easy to run PG in this environment
> is a bad idea. If you've got namespacing or other stuff that can
> inhibit the ability of one would-be postmaster to see another one,
> you are playing with fire. You need to not run things that way, or
> someday you'll find your data eaten.

Maybe, but such setups are increasingly common. I'm not sure that we
can just tell people "don't do that"; I think everyone already is.

I also feel like it's counterintuitive that pg_upgrade --check can
destroy data, regardless of anything else. One could certainly fail to
read the documentation and fail to realize that risk.

None of this is to say that I have a good idea, because I don't.

--
Robert Haas
Databricks

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2026-11-16 21:51:58 Re: BUG #19908: pg_upgrade --check crashes instance if running in a different PID Namespace then the old cluster
Previous Message Adam Matthews 2026-11-16 20:51:25 16.16: join order regression for pg_indexes self-join (schema filter applied last), ~50x slower than 16.15