From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Jeff Davis <jdavis(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
Date: | 2023-06-10 00:37:57 |
Message-ID: | d20864b929ff769a0ebf772359719f05bb6982cd.camel@j-davis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Fri, 2023-06-09 at 15:16 -0700, Jeff Davis wrote:
> On Fri, 2023-06-09 at 20:54 +0000, Jeff Davis wrote:
> > Fix search_path to a safe value during maintenance operations.
>
> Looks like this is causing pg_amcheck failures in the buildfarm.
> Investigating...
It looks related to bt_index_check_internal(), which is called by SQL
functions bt_index_check() and bt_index_parent_check(). SQL functions
can be called in parallel, so it raises the error:
ERROR: cannot set parameters during a parallel operation
because commit 05e1737351 added the SetConfigOption() line. Normally
those functions would not be called in parallel, but
debug_parallel_mode makes that happen.
Attached a patch to mark those functions as PARALLEL UNSAFE, which
fixes the problem.
Alternatively, I could just take out that line, as those SQL functions
are not controlled by the MAINTAIN privilege. But for consistency I
think it's a good idea to leave it in so that index functions are
called with the right search path for amcheck.
--
Jeff Davis
PostgreSQL Contributor Team - AWS
Attachment | Content-Type | Size |
---|---|---|
v1-0001-amcheck-mark-bt_index_check-PARALLEL-UNSAFE.patch | text/x-patch | 2.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2023-06-10 00:49:00 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
Previous Message | Jeff Davis | 2023-06-09 22:16:11 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Smith | 2023-06-10 00:41:50 | Re: Use COPY for populating all pgbench tables |
Previous Message | Bruce Momjian | 2023-06-10 00:23:08 | Re: Let's make PostgreSQL multi-threaded |