Re: Report planning memory in EXPLAIN ANALYZE

On 2024-Jan-18, Ashutosh Bapat wrote:

> The EXPLAIN output produces something like below
>                        explain_filter
>   ---------------------------------------------------------
>    Seq Scan on int8_tbl i8  (cost=N.N..N.N rows=N width=N)
>   Planning:
>     Memory: used=N bytes, allocated=N bytes
>  (3 rows)
> 
> but function explain_filter(), defined in explain.sql, removes line
> containing Planning: and we end up with output
>                        explain_filter
>   ---------------------------------------------------------
>    Seq Scan on int8_tbl i8  (cost=N.N..N.N rows=N width=N)
>     Memory: used=N bytes, allocated=N bytes
>  (2 rows)
> 
> Hence this weird difference.

Ah, okay, that makes sense.  (I actually think this is a bit insane, and
I would hope that we can revert commit eabba4a3eb71 eventually, but I
don't think that needs to hold up your proposed patch.)

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"At least to kernel hackers, who really are human, despite occasional
rumors to the contrary" (LWN.net)