diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2024-01-29 17:53:03 +0100 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2024-01-29 17:53:03 +0100 |
| commit | 5de890e3610d5a12cdaea36413d967cf5c544e20 (patch) | |
| tree | fa419c222f2f3c59c2e478ea305e21e6f1d05c66 /src/backend/utils/adt/xml.c | |
| parent | 6a1ea02c491d16474a6214603dce40b5b122d4d1 (diff) | |
| download | postgresql-5de890e3610d5a12cdaea36413d967cf5c544e20.tar.gz postgresql-5de890e3610d5a12cdaea36413d967cf5c544e20.zip | |
Add EXPLAIN (MEMORY) to report planner memory consumption
This adds a new "Memory:" line under the "Planning:" group (which
currently only has "Buffers:") when the MEMORY option is specified.
In order to make the reporting reasonably accurate, we create a separate
memory context for planner activities, to be used only when this option
is given. The total amount of memory allocated by that context is
reported as "allocated"; we subtract memory in the context's freelists
from that and report that result as "used". We use
MemoryContextStatsInternal() to obtain the quantities.
The code structure to show buffer usage during planning was not in
amazing shape, so I (Álvaro) modified the patch a bit to clean that up
in passing.
Author: Ashutosh Bapat
Reviewed-by: David Rowley, Andrey Lepikhov, Jian He, Andy Fan
Discussion: https://www.postgresql.org/message-id/CAExHW5sZA=5LJ_ZPpRO-w09ck8z9p7eaYAqq3Ks9GDfhrxeWBw@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/xml.c')
0 files changed, 0 insertions, 0 deletions