| From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
|---|---|
| To: | Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> |
| Cc: | Lepikhov Andrei <a(dot)lepikhov(at)postgrespro(dot)ru>, jian he <jian(dot)universality(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Report planning memory in EXPLAIN ANALYZE |
| Date: | 2023-10-30 14:43:30 |
| Message-ID: | CAExHW5sCJX7696sF-OnugAiaXS=Ag95=-m1cSrjcmyYj8Pduuw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
>
> David challenged something at the begining, but IIUC he also agree the
> value of patch 01 as the previous statement after discussion. Since the patch
> is mild itself, so I will mark this commitfest entry as "Ready for committer".
> Please correct me if anything is wrong.
>
Thanks Andy.
Here's rebased patches. A conflict in explain.out resolved.
--
Best Wishes,
Ashutosh Bapat
| Attachment | Content-Type | Size |
|---|---|---|
| 0002-Report-memory-allocated-along-with-memory-u-20231030.patch | text/x-patch | 13.8 KB |
| 0003-Separate-memory-context-for-planner-s-memor-20231030.patch | text/x-patch | 3.9 KB |
| 0001-Report-memory-used-for-planning-a-query-in--20231030.patch | text/x-patch | 10.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-10-30 14:45:03 | Re: trying again to get incremental backup |
| Previous Message | Ashutosh Bapat | 2023-10-30 14:36:13 | Re: Not deleted mentions of the cleared path |