| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted |
| Date: | 2016-06-10 00:17:43 |
| Message-ID: | 21680.1465517863@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
I wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> There's one other related thing I'm concerned about, which is that the
>> code in namespace.c that manages pg_temp doesn't know anything about
>> parallelism. So it will interpret pg_temp to mean the pg_temp_NNN
>> schema for its own backend ID rather than the leader's backend ID.
>> I'm not sure that's a problem, but I haven't thought deeply about it.
> Hmmm. I'll take a look.
Yeah, that was pretty broken, but I believe I've fixed it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2016-06-10 13:22:26 | Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted |
| Previous Message | Tom Lane | 2016-06-10 00:16:18 | pgsql: Improve the situation for parallel query versus temp relations. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-06-10 00:19:34 | Re: Perf Benchmarking and regression. |
| Previous Message | Tatsuo Ishii | 2016-06-09 23:16:42 | Re: parallel workers and client encoding |