| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Restrict the use of temporary namespace in two-phase transaction |
| Date: | 2019-01-18 01:08:07 |
| Message-ID: | 25291.1547773687@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-01-18 01:52:48 | pgsql: Enforce non-parallel plan when calling current_schema() in newly |
| Previous Message | Michael Paquier | 2019-01-18 00:59:49 | Re: pgsql: Restrict the use of temporary namespace in two-phase transaction |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-01-18 01:09:20 | Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages) |
| Previous Message | Dave Cramer | 2019-01-18 01:01:44 | Re: Libpq support to connect to standby server as priority |