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: Dilip Kumar <dilipbalaut@gmail.com>

Cc: maximilian.chrzan@here.com, pgsql-bugs@lists.postgresql.org

Date: 2025-06-20T17:50:41Z

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

Dilip Kumar <dilipbalaut@gmail.com> 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