Re: pgsql: Restrict the use of temporary namespace in two-phase transaction - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Restrict the use of temporary namespace in two-phase transaction
Date
Msg-id 25291.1547773687@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Restrict the use of temporary namespace in two-phasetransaction  (Michael Paquier <michael@paquier.xyz>)
List pgsql-committers
Michael Paquier <michael@paquier.xyz> writes:
> I have been monitoring the buildfarm and crake is complaining:
> https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=crake&br=HEAD

> I am actually amazed to see the planner choose a parallel plan for
> that,

That's due to force_parallel_mode = regress, I imagine.

> Anyway, it seems to me that this is pointing out to another issue:
> current_schema() can trigger a namespace creation, hence shouldn't we
> mark it as PARALLEL UNSAFE and make sure that we never run into this
> problem?

That seems a bit annoying, but maybe we have little choice?

            regards, tom lane


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pgsql: Restrict the use of temporary namespace in two-phasetransaction
Next
From: Michael Paquier
Date:
Subject: pgsql: Enforce non-parallel plan when calling current_schema() innewly