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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Dilip Kumar <dilipbalaut@gmail.com>, maximilian.chrzan@here.com, pgsql-hackers@lists.postgresql.org

Date: 2025-09-16T02:08:40Z

Lists: pgsql-bugs, pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Improve the names generated for indexes on expressions.
- 181b6185c79e master landed
Use SnapshotDirty when checking for conflicting index names.
- fdd82692230a 17.6 landed
- 75b8982eae78 15.14 landed
- 5861b1f343b5 18.0 landed
- 4b66cb18879e 13.22 landed
- 27af8b9be8c0 14.19 landed
- 1e24ea160350 16.10 landed
Change the names generated for child foreign key constraints.
- 3db61db48ef5 18.0 cited

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