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

From Robert Haas
Subject Re: pgsql: Restrict the use of temporary namespace in two-phase transaction
Date
Msg-id CA+TgmoZaCNTxXzV76zuyMuc8N9vU6RgEhVu8t9dXDcKqThUW7A@mail.gmail.com
Whole thread Raw
Responses Re: pgsql: Restrict the use of temporary namespace in two-phase transaction  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pgsql: Restrict the use of temporary namespace in two-phase transaction  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Thu, Jan 17, 2019 at 8:08 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > 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?

The only other option I see is to make current_schema() not trigger a
namespace creation.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] pgbench tap tests fail if the path contains a perl special character
Next
From: Robert Haas
Date:
Subject: Re: New vacuum option to do only freezing