Re: explain format json, unit for serialize and memory are different. - Mailing list pgsql-hackers

From jian he
Subject Re: explain format json, unit for serialize and memory are different.
Date
Msg-id CACJufxE+4sDYA=A94Wyh4gmL=W8p_sWa4GvELp-cy1-50=8EjQ@mail.gmail.com
Whole thread Raw
In response to Re: explain format json, unit for serialize and memory are different.  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: explain format json, unit for serialize and memory are different.
List pgsql-hackers
On Wed, May 15, 2024 at 10:13 AM David Rowley <dgrowleyml@gmail.com> wrote:
>
> 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.
>

looking at serializeAnalyzeReceive.
I am not sure which part of serializeAnalyzeReceive will update pgBufferUsage.

I am looking for an example where this information under json key
"Serialization" is not zero.
So far I have tried:

create table s(a text);
insert into s select repeat('a', 1024) from generate_series(1,1024);
explain (format json, analyze, wal, buffers, memory, serialize, timing
off)  select * from s;



pgsql-hackers by date:

Previous
From: "Imseih (AWS), Sami"
Date:
Subject: Re: query_id, pg_stat_activity, extended query protocol
Next
From: Michael Paquier
Date:
Subject: Re: Fix src/test/subscription/t/029_on_error.pl test when wal_debug is enabled