| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | parallel.sgml for Gather with InitPlans |
| Date: | 2018-05-07 17:37:09 |
| Message-ID: | CA+Tgmoa+vupW8V_gBonz6hU7WwN2zJ=UTsVWCVB+rN6vaaXfZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
In the wake of commit e89a71fb449af2ef74f47be1175f99956cf21524,
parallel.sgml is no longer correct about the effect of InitPlans:
<para>
The following operations are always parallel restricted.
</para>
...
<para>
Access to an <literal>InitPlan</literal> or correlated
<literal>SubPlan</literal>.
</para>
I thought about this a bit and came up with the attached patch. Other ideas?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| parallel-initplan.patch | application/octet-stream | 645 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-05-07 17:49:35 | Re: Explain buffers wrong counter with parallel plans |
| Previous Message | Robert Haas | 2018-05-07 17:23:32 | Re: [HACKERS] Parallel Append implementation |