| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Add mention of execution time memory for enable_partitionwise_* GUCs |
| Date: | 2024-07-17 22:33:35 |
| Message-ID: | CAApHDvoZ0_yqwPFEpb6h261L76BUpmh5GxBQq0LeRzQ5Jh3zzg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Over on [1], there's a complaint about a query OOMing because the use
of enable_partitionwise_aggregate caused a plan with 1000 Hash
Aggregate nodes.
The only mention in the docs is the additional memory requirements and
CPU for query planning when that GUC is enabled. There's no mention
that execution could use work_mem * nparts more memory to be used. I
think that's bad and we should fix it.
I've attached my proposal to fix that.
David
[1] https://postgr.es/m/3603c380-d094-136e-e333-610914fb3e80%40gmx.net
| Attachment | Content-Type | Size |
|---|---|---|
| enable_partitionwise_doc_change.patch | application/octet-stream | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Zhang | 2024-07-17 22:41:55 | Re: Proposal for implementing OCSP Stapling in PostgreSQL |
| Previous Message | Noah Misch | 2024-07-17 22:03:26 | Re: Built-in CTYPE provider |