| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Restrict the use of temporary namespace in two-phase transaction |
| Date: | 2019-01-18 20:05:02 |
| Message-ID: | CA+TgmoZaCNTxXzV76zuyMuc8N9vU6RgEhVu8t9dXDcKqThUW7A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Thu, Jan 17, 2019 at 8:08 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-01-18 20:06:49 | pgsql: Use our own getopt() on OpenBSD. |
| Previous Message | Alvaro Herrera | 2019-01-18 18:07:28 | pgsql: Move CloneForeignKeyConstraints to tablecmds.c |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-01-18 20:07:50 | Re: New vacuum option to do only freezing |
| Previous Message | Tom Lane | 2019-01-18 20:02:46 | Re: [PATCH] pgbench tap tests fail if the path contains a perl special character |