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

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: explain format json, unit for serialize and memory are different.
Date: 2024-05-13 09:16:24
Message-ID: CACJufxE4Sp7xvgOwhqtFx5hS85AxMKobPWDo-xZHZVTpK3EBjA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

hi.

explain(analyze, format json, serialize, memory, costs off, Timing
off) select * from tenk1;
QUERY PLAN
---------------------------------
[
{
"Plan": {
"Node Type": "Seq Scan",
"Parallel Aware": false,
"Async Capable": false,
"Relation Name": "tenk1",
"Alias": "tenk1",
"Actual Rows": 10000,
"Actual Loops": 1
},
"Planning": {
"Memory Used": 23432,
"Memory Allocated": 65536
},
"Planning Time": 0.290,
"Triggers": [
],
"Serialization": {
"Output Volume": 1143,
"Format": "text"
},
"Execution Time": 58.814
}
]

explain(analyze, format text, serialize, memory, costs off, Timing
off) select * from tenk1;
QUERY PLAN
---------------------------------------------------
Seq Scan on tenk1 (actual rows=10000 loops=1)
Planning:
Memory: used=23432 bytes allocated=65536 bytes
Planning Time: 0.289 ms
Serialization: output=1143kB format=text
Execution Time: 58.904 ms

under format json, "Output Volume": 1143,
1143 is kiB unit, and is not the same as "Memory Used" or "Memory
Allocated" byte unit.

Do we need to convert it to byte for the non-text format option for EXPLAIN?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2024-05-13 09:19:08 Re: Parallel CREATE INDEX for GIN indexes
Previous Message Peter Eisentraut 2024-05-13 08:48:53 doc: some fixes for environment sections in ref pages