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-15 20:06:26 |
Message-ID: | 658984.1757966786@sss.pgh.pa.us |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Sep 15, 2025 at 12:15 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So, how do we move forward? I'm perfectly willing to look into
>> the derive-a-name-from-the-expression idea, but I think that'd
>> best be done in a separate patch.
> I'm not sure. To me, the munging of everything together under the name
> "expr" is the root of the problem here, and since this patch isn't
> really addressing that problem, it's kind of to one side of what I see
> as the main point. However, that's a judgement call, and if you or
> others see it differently, then so be it.
Well, let's leave it as a difference of opinion for the moment.
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2025-09-15 20:30:17 | Re: BUG #19054: Memory exhaustion vulnerability in PostgreSQL array operations leads to server crash |
Previous Message | PG Bug reporting form | 2025-09-15 20:00:12 | BUG #19054: Memory exhaustion vulnerability in PostgreSQL array operations leads to server crash |
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Mityugov | 2025-09-15 20:08:28 | Re: --with-llvm on 32-bit platforms? |
Previous Message | Tom Lane | 2025-09-15 20:01:47 | Re: Identifying function-lookup failures due to argument name mismatches |