From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | jian he <jian(dot)universality(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: explain format json, unit for serialize and memory are different. |
Date: | 2024-05-15 02:13:00 |
Message-ID: | CAApHDvo=g0UjmWNdGmnkU3aLpx+ZA3UnHfwTzWk1hzCNCbMw3Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 15 May 2024 at 13:44, jian he <jian(dot)universality(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2024-05-15 02:20:11 | Re: First draft of PG 17 release notes |
Previous Message | Michael Paquier | 2024-05-15 02:07:21 | Re: Postgres and --config-file option |