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

Поиск
Список
Период
Сортировка
От jian he
Тема explain format json, unit for serialize and memory are different.
Дата
Msg-id CACJufxE4Sp7xvgOwhqtFx5hS85AxMKobPWDo-xZHZVTpK3EBjA@mail.gmail.com
обсуждение исходный текст
Ответы Re: explain format json, unit for serialize and memory are different.
Список 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?



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: doc: some fixes for environment sections in ref pages
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: Parallel CREATE INDEX for GIN indexes