From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Parallel query behaving different with custom GUCs |
Date: | 2023-11-09 04:01:09 |
Message-ID: | ZUxZhZfO4ADfi8D8@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Oct 30, 2023 at 09:21:56AM -0400, Robert Haas wrote:
> I'm also alert to my own possible bias. Perhaps since I designed this
> mechanism, I'm more prone to viewing its deficiencies as minor than a
> neutral observer would be. So if anyone is sitting there reading this
> and thinking "wow, I can't believe Robert doesn't think it's important
> to fix this," feel free to write back and say so.
Fun. Agreed that this is a bug, and that the consequences are of
null for most users. And it took 7 years to find that.
If I may ask, is there an impact with functions that include SET
clauses with custom parameters that are parallel safe? Saying that,
if the fix is simple, I see no reason not to do something about it,
even if that's HEAD-only.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2023-11-09 04:23:07 | Re: A recent message added to pg_upgade |
Previous Message | Michael Paquier | 2023-11-09 03:58:04 | Re: Doubled test for SET statements in pg_stat_statements tests |