Re: Crashes on a partition whose concurrent detach never finished

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Zhijie Hou <houzhijie22(at)gmail(dot)com>
Cc: shveta malik <shveta(dot)malik(at)gmail(dot)com>, Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, "ashutosh(dot)bapat(dot)oss(at)gmail(dot)com" <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, shveta malik <shvetamalik(at)gmail(dot)com>
Subject: Re: Crashes on a partition whose concurrent detach never finished
Date: 2026-11-12 11:10:13
Message-ID: avWd3g4diunavzX5@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-Nov-12, Zhijie Hou wrote:

> Since there's only one publication in this file, I think the current name is
> fine as we don't need to distinguish it from any other publication. Similar
> names are also used in other tests.

Right now, isolation tests run one after the other, so you're right that
this name doesn't really matter much. However, someday it might be nice
if we can make (some of) them run in parallel. We tried to do that eons
ago, couldn't find the time to implement it, idea was forgotten. If
that effort ever takes off again it would be nice if we don't have to
fix a thousand pointless name conflicts of this kind. (We already have
enough of those that we'll have to fix.) So I think Shveta had the
right idea here.

Anyway, thanks everybody for getting this fixed.

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"The problem with the future is that it keeps turning into the present"
(Hobbes)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-11-12 11:16:53 SIGFPE handling
Previous Message Hayato Kuroda (Fujitsu) 2026-11-12 10:41:11 RE: Hash index: stop registering pin-only bucket pages in WAL (remove REGBUF_NO_CHANGE)