pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC 7+ messages / 1 participants [nested] [flat]
* pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC @ 2024-07-31 13:26 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: David Rowley @ 2024-07-31 13:26 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Doc: mention executor memory usage for enable_partitionwise* GUCs Prior to this commit, the docs for enable_partitionwise_aggregate and enable_partitionwise_join mentioned the additional overheads enabling these causes for the query planner, but they mentioned nothing about the possible surge in work_mem-consuming executor nodes that could end up in the final plan. Dimitrios reported the OOM killer intervened on his query as a result of using enable_partitionwise_aggregate=on. Here we adjust the docs to mention the possible increase in the number of work_mem-consuming executor nodes that can appear in the final plan as a result of enabling these GUCs. Reported-by: Dimitrios Apostolou Reviewed-by: Ashutosh Bapat Discussion: https://postgr.es/m/3603c380-d094-136e-e333-610914fb3e80%40gmx.net Discussion: https://postgr.es/m/CAApHDvoZ0_yqwPFEpb6h261L76BUpmh5GxBQq0LeRzQ5Jh3zzg@mail.gmail.com Backpatch-through: 12, oldest supported version Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/057ee9183c2142f6ecd9035aa6b96c5509c18a27 Modified Files -------------- doc/src/sgml/config.sgml | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC @ 2024-07-31 13:26 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: David Rowley @ 2024-07-31 13:26 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Doc: mention executor memory usage for enable_partitionwise* GUCs Prior to this commit, the docs for enable_partitionwise_aggregate and enable_partitionwise_join mentioned the additional overheads enabling these causes for the query planner, but they mentioned nothing about the possible surge in work_mem-consuming executor nodes that could end up in the final plan. Dimitrios reported the OOM killer intervened on his query as a result of using enable_partitionwise_aggregate=on. Here we adjust the docs to mention the possible increase in the number of work_mem-consuming executor nodes that can appear in the final plan as a result of enabling these GUCs. Reported-by: Dimitrios Apostolou Reviewed-by: Ashutosh Bapat Discussion: https://postgr.es/m/3603c380-d094-136e-e333-610914fb3e80%40gmx.net Discussion: https://postgr.es/m/CAApHDvoZ0_yqwPFEpb6h261L76BUpmh5GxBQq0LeRzQ5Jh3zzg@mail.gmail.com Backpatch-through: 12, oldest supported version Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/3256722d7b7ff64918a0e5fdf6140de355147fe6 Modified Files -------------- doc/src/sgml/config.sgml | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC @ 2024-07-31 13:27 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: David Rowley @ 2024-07-31 13:27 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Doc: mention executor memory usage for enable_partitionwise* GUCs Prior to this commit, the docs for enable_partitionwise_aggregate and enable_partitionwise_join mentioned the additional overheads enabling these causes for the query planner, but they mentioned nothing about the possible surge in work_mem-consuming executor nodes that could end up in the final plan. Dimitrios reported the OOM killer intervened on his query as a result of using enable_partitionwise_aggregate=on. Here we adjust the docs to mention the possible increase in the number of work_mem-consuming executor nodes that can appear in the final plan as a result of enabling these GUCs. Reported-by: Dimitrios Apostolou Reviewed-by: Ashutosh Bapat Discussion: https://postgr.es/m/3603c380-d094-136e-e333-610914fb3e80%40gmx.net Discussion: https://postgr.es/m/CAApHDvoZ0_yqwPFEpb6h261L76BUpmh5GxBQq0LeRzQ5Jh3zzg@mail.gmail.com Backpatch-through: 12, oldest supported version Branch ------ REL_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/a459e583e06b640597c2e24ab6043a0701a5a545 Modified Files -------------- doc/src/sgml/config.sgml | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC @ 2024-07-31 13:27 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: David Rowley @ 2024-07-31 13:27 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Doc: mention executor memory usage for enable_partitionwise* GUCs Prior to this commit, the docs for enable_partitionwise_aggregate and enable_partitionwise_join mentioned the additional overheads enabling these causes for the query planner, but they mentioned nothing about the possible surge in work_mem-consuming executor nodes that could end up in the final plan. Dimitrios reported the OOM killer intervened on his query as a result of using enable_partitionwise_aggregate=on. Here we adjust the docs to mention the possible increase in the number of work_mem-consuming executor nodes that can appear in the final plan as a result of enabling these GUCs. Reported-by: Dimitrios Apostolou Reviewed-by: Ashutosh Bapat Discussion: https://postgr.es/m/3603c380-d094-136e-e333-610914fb3e80%40gmx.net Discussion: https://postgr.es/m/CAApHDvoZ0_yqwPFEpb6h261L76BUpmh5GxBQq0LeRzQ5Jh3zzg@mail.gmail.com Backpatch-through: 12, oldest supported version Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/27146e79bf0301969945d73388f430fa8ff08870 Modified Files -------------- doc/src/sgml/config.sgml | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC @ 2024-07-31 13:28 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: David Rowley @ 2024-07-31 13:28 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Doc: mention executor memory usage for enable_partitionwise* GUCs Prior to this commit, the docs for enable_partitionwise_aggregate and enable_partitionwise_join mentioned the additional overheads enabling these causes for the query planner, but they mentioned nothing about the possible surge in work_mem-consuming executor nodes that could end up in the final plan. Dimitrios reported the OOM killer intervened on his query as a result of using enable_partitionwise_aggregate=on. Here we adjust the docs to mention the possible increase in the number of work_mem-consuming executor nodes that can appear in the final plan as a result of enabling these GUCs. Reported-by: Dimitrios Apostolou Reviewed-by: Ashutosh Bapat Discussion: https://postgr.es/m/3603c380-d094-136e-e333-610914fb3e80%40gmx.net Discussion: https://postgr.es/m/CAApHDvoZ0_yqwPFEpb6h261L76BUpmh5GxBQq0LeRzQ5Jh3zzg@mail.gmail.com Backpatch-through: 12, oldest supported version Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/51895d08b41a5e5ed7e7a477fb5aa36213347ea7 Modified Files -------------- doc/src/sgml/config.sgml | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC @ 2024-07-31 13:28 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: David Rowley @ 2024-07-31 13:28 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Doc: mention executor memory usage for enable_partitionwise* GUCs Prior to this commit, the docs for enable_partitionwise_aggregate and enable_partitionwise_join mentioned the additional overheads enabling these causes for the query planner, but they mentioned nothing about the possible surge in work_mem-consuming executor nodes that could end up in the final plan. Dimitrios reported the OOM killer intervened on his query as a result of using enable_partitionwise_aggregate=on. Here we adjust the docs to mention the possible increase in the number of work_mem-consuming executor nodes that can appear in the final plan as a result of enabling these GUCs. Reported-by: Dimitrios Apostolou Reviewed-by: Ashutosh Bapat Discussion: https://postgr.es/m/3603c380-d094-136e-e333-610914fb3e80%40gmx.net Discussion: https://postgr.es/m/CAApHDvoZ0_yqwPFEpb6h261L76BUpmh5GxBQq0LeRzQ5Jh3zzg@mail.gmail.com Backpatch-through: 12, oldest supported version Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/5eea78af2d3c0f78b97bcaa036bccd9b28b96592 Modified Files -------------- doc/src/sgml/config.sgml | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC @ 2024-07-31 13:29 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: David Rowley @ 2024-07-31 13:29 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Doc: mention executor memory usage for enable_partitionwise* GUCs Prior to this commit, the docs for enable_partitionwise_aggregate and enable_partitionwise_join mentioned the additional overheads enabling these causes for the query planner, but they mentioned nothing about the possible surge in work_mem-consuming executor nodes that could end up in the final plan. Dimitrios reported the OOM killer intervened on his query as a result of using enable_partitionwise_aggregate=on. Here we adjust the docs to mention the possible increase in the number of work_mem-consuming executor nodes that can appear in the final plan as a result of enabling these GUCs. Reported-by: Dimitrios Apostolou Reviewed-by: Ashutosh Bapat Discussion: https://postgr.es/m/3603c380-d094-136e-e333-610914fb3e80%40gmx.net Discussion: https://postgr.es/m/CAApHDvoZ0_yqwPFEpb6h261L76BUpmh5GxBQq0LeRzQ5Jh3zzg@mail.gmail.com Backpatch-through: 12, oldest supported version Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/447e25c049150a0954b0532393de24916a1b7479 Modified Files -------------- doc/src/sgml/config.sgml | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2024-07-31 13:29 UTC | newest] Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-07-31 13:26 pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC David Rowley <drowley@postgresql.org> 2024-07-31 13:26 pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC David Rowley <drowley@postgresql.org> 2024-07-31 13:27 pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC David Rowley <drowley@postgresql.org> 2024-07-31 13:27 pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC David Rowley <drowley@postgresql.org> 2024-07-31 13:28 pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC David Rowley <drowley@postgresql.org> 2024-07-31 13:28 pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC David Rowley <drowley@postgresql.org> 2024-07-31 13:29 pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC David Rowley <drowley@postgresql.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox