Re: Detoasting optionally to make Explain-Analyze less misleading - Mailing list pgsql-hackers

From Jehan-Guillaume de Rorthais
Subject Re: Detoasting optionally to make Explain-Analyze less misleading
Date
Msg-id 20230913130904.7386a230@karst
Whole thread Raw
In response to Re: Detoasting optionally to make Explain-Analyze less misleading  (stepan rutz <stepan.rutz@gmx.de>)
List 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




pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Have better wording for snapshot file reading failure
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Synchronizing slots from primary to standby