Re: explain format json, unit for serialize and memory are different.

David Rowley <dgrowleyml@gmail.com>

From: David Rowley <dgrowleyml@gmail.com>
To: jian he <jian.universality@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Michael Paquier <michael@paquier.xyz>, Daniel Gustafsson <daniel@yesql.se>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2024-05-15T02:13:00Z
Lists: pgsql-hackers
On Wed, 15 May 2024 at 13:44, jian he <jian.universality@gmail.com> wrote:
>        "Shared Hit Blocks": 0,
>        "Shared Read Blocks": 0,
>        "Shared Dirtied Blocks": 0,
>        "Shared Written Blocks": 0,
>        "Local Hit Blocks": 0,
>        "Local Read Blocks": 0,
>        "Local Dirtied Blocks": 0,
>        "Local Written Blocks": 0,
>        "Temp Read Blocks": 0,
>        "Temp Written Blocks": 0
>
> these information duplicated for json key "Serialization" and json key
> "Planning"
> i am not sure this is intended?

Looks ok to me.  Buffers used during planning are independent from the
buffers used when outputting rows to the client.

David



Commits

  1. Fix some inconsistencies in EXPLAIN output