Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uSft3-00BWqi-Qp for pgsql-bugs@arkaria.postgresql.org; Fri, 20 Jun 2025 17:50:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uSft1-003TVi-5u for pgsql-bugs@arkaria.postgresql.org; Fri, 20 Jun 2025 17:50:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uSft0-003TUN-SD for pgsql-bugs@lists.postgresql.org; Fri, 20 Jun 2025 17:50:47 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uSfsz-0035uQ-2N for pgsql-bugs@lists.postgresql.org; Fri, 20 Jun 2025 17:50:46 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 55KHofdP2139687; Fri, 20 Jun 2025 13:50:41 -0400 From: Tom Lane To: Dilip Kumar cc: maximilian.chrzan@here.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. In-reply-to: References: <18959-f63b53b864bb1417@postgresql.org> <1081051.1750260111@sss.pgh.pa.us> <1138732.1750265195@sss.pgh.pa.us> <1802526.1750366786@sss.pgh.pa.us> Comments: In-reply-to Dilip Kumar message dated "Fri, 20 Jun 2025 16:59:10 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2139685.1750441841.1@sss.pgh.pa.us> Date: Fri, 20 Jun 2025 13:50:41 -0400 Message-ID: <2139686.1750441841@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Dilip Kumar writes: > Yes, that makes sense to apply in v19 because of user visible behavior > changes in index names. I agree the SnapshotDirty patch can give > relief for this case for back branches. OK, I pushed the SnapshotDirty patch. The other patch still seems to apply over it, so I won't repost that unless the cfbot thinks differently. regards, tom lane