Re: Report planning memory in EXPLAIN ANALYZE - Mailing list pgsql-hackers

From Abhijit Menon-Sen
Subject Re: Report planning memory in EXPLAIN ANALYZE
Date
Msg-id ZaF1fB_hMqycSq-S@toroid.org
Whole thread Raw
In response to Re: Report planning memory in EXPLAIN ANALYZE  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
At 2024-01-12 17:52:27 +0100, alvherre@alvh.no-ip.org wrote:
>
> I think this patch is mostly OK

(After the last few rounds of changes, it looks fine to me too.)

>  Planning:
>    Buffers: shared hit=120 read=30
>    Memory: used=67944 bytes allocated=73728 bytes
>  Planning Time: 0.892 ms
>
> […]
>
> Or we could leave it as you have it, but to me that's akin to giving up
> on doing it nicely.

For completeness, there's a third option, which is easier to write and a
bit more friendly to the sort of thing that might already be parsing
"Planning Time", viz.,

    Planning Buffers: shared hit=120 read=30
    Planning Memory: used=67944 bytes allocated=73728 bytes
    Planning Time: 0.892 ms

(Those "bytes" look slightly odd to me in the midst of all the x=y
pieces, but that's probably not worth thinking about.)

-- Abhijit



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: introduce dynamic shared memory registry
Next
From: Nathan Bossart
Date:
Subject: Re: reorganize "Shared Memory and LWLocks" section of docs