From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Restrict the use of temporary namespace in two-phase transaction
Date: Thu, 17 Jan 2019 20:08:07 -0500
Message-ID: <25291.1547773687@sss.pgh.pa.us> (raw)
In-Reply-To: <20190118005949.GD1883@paquier.xyz>
References: <E1gkHvw-00010c-3O@gemulon.postgresql.org>
<20190118005949.GD1883@paquier.xyz>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Restrict the use of temporary namespace in two-phase transaction
In-Reply-To: <25291.1547773687@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox