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: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: maximilian(dot)chrzan(at)here(dot)com, pgsql-bugs(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-06-20 17:50:41
Message-ID: 2139686.1750441841@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Dilip Kumar <dilipbalaut(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2025-06-20 18:14:22 Re: BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions
Previous Message PG Bug reporting form 2025-06-20 17:42:06 BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions