| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-19 12:38:38 |
| Message-ID: | 7122257E-AF41-4B63-BC37-95B20FEBB974@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 16 Nov 2026, at 22:36, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> 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.
I wasn't able to come up with a good idea either, but I propose that we at
least add a note to the documentation. How about something like the attached
to at least make it visible until we have a solution?
--
Daniel Gustafsson
| Attachment | Content-Type | Size |
|---|---|---|
| pg_upgrade_processpace.diff | application/octet-stream | 902 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Rachitskiy | 2026-11-19 13:00:05 | Re: BUG #19918: SIGSEGV in auto_explain + EXPLAIN (BUFFERS) |
| Previous Message | Fujii Masao | 2026-11-19 12:31:24 | Re: BUG #19918: SIGSEGV in auto_explain + EXPLAIN (BUFFERS) |