| From: | James Coleman <jtc331(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Parallel safety docs for CTEs |
| Date: | 2024-11-19 19:16:59 |
| Message-ID: | CAAaqYe_TjZugK5JmiBfNHBKEDi5N+AeQ5UNGisWcqe7wvtQy4Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
A colleague noticed today that the docs still say that "Scans of
common table expressions (CTEs)" are "always parallel restricted".
While I think that strictly remains true at the implementation level,
from a user's perspective I think that's not been true since the
change to default to trying to inline CTEs rather than defaulting to
materializing them.
Attached is a patch to slightly modify the language; would be happy to
hear suggestions on a better way to improve this.
Regards,
James Coleman
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Update-parallel-safety-docs-for-CTE-optimizations.patch | application/octet-stream | 795 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2024-11-19 19:28:03 | Re: Parametrization minimum password lenght |
| Previous Message | Pavel Stehule | 2024-11-19 19:14:01 | Re: proposal: schema variables |