Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, maximilian(dot)chrzan(at)here(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
Date: 2025-09-16 02:08:40
Message-ID: 877999.1757988520@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

I wrote:
> I do agree that improving the names generated for expression indexes
> would be useful independently of this. I propose setting this patch
> aside for the time being, and I will go look into that, and then
> if that gets accepted we can come back here and discuss how much
> of a problem remains.

I started a separate thread for that, mostly so the cfbot doesn't
see it as the same patch:

https://www.postgresql.org/message-id/flat/876799.1757987810%40sss.pgh.pa.us

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-09-16 02:29:58 Re: question about pending updates in pgstat_report_inj
Previous Message Tom Lane 2025-09-16 01:56:50 Improving the names generated for indexes on expressions

Browse pgsql-bugs by date

  From Date Subject
Previous Message Richard Guo 2025-09-16 01:05:37 Re: BUG #19046: Incorrect result when using json_array() with column reference in subquery combined with RIGHT JOIN