Re: Parallel safety for extern params

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Parallel safety for extern params
Date: 2025-03-21 16:21:13
Message-ID: CA+TgmoarjCSoz+D2Cbf4YkJTs_3FLV3xegGxE4f5LAykjkyqDQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 21, 2025 at 11:52 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I think this is completely wrong and should be reverted. There
> cannot be a Param there, and if there were it would not represent
> a reference to the Gather's child.
>
> I tried reverting this code change, and check-world still passes,
> with or without debug_parallel_query = regress. So if there is
> a case I'm missing, the regression tests don't expose it.

Did you try the test case from the original post on this thread?

I'm perfectly willing to believe that we messed up here -- this was 8
years ago and I don't remember the details -- but it surprises me a
little bit that I would have committed that change without verifying
that it was necessary to resolve the reported problem. However, I have
made such mistakes before and will probably make them again, so it
certainly could have happened.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Berg 2025-03-21 16:26:20 Re: query_id: jumble names of temp tables for better pg_stat_statement UX
Previous Message Bertrand Drouvot 2025-03-21 16:18:02 Re: Fix 035_standby_logical_decoding.pl race conditions