Horton

Re: Detoasting optionally to make Explain-Analyze less misleading

Jehan-Guillaume de Rorthais <jgdr@dalibo.com>

View thread View on postgr.es
From: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
To: stepan rutz <stepan.rutz@gmx.de>
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>, pgsql-hackers@postgresql.org
Date: 2023-09-13T11:09:04Z
Lists: pgsql-hackers 
Hi Stepan & all,

On Tue, 12 Sep 2023 17:16:00 +0200
stepan rutz <stepan.rutz@gmx.de> wrote:

...
> Attached a new patch. Hoping for feedback,

Nice addition to EXPLAIN!

On the feature front, what about adding the actual detoasting/serializing time
in the explain output?

That could be:

  =>  explain (analyze,serialize,costs off,timing off) 
      select * from test_detoast;
                        QUERY PLAN                        
  ─────────────────────────────────────────────────────────
   Seq Scan on public.test_detoast (actual rows=Nv loops=N)
   Planning Time: N ms
   Execution Time: N ms
   Serialize Time: N ms

Commits

  1. Invent SERIALIZE option for EXPLAIN.