From: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
To: stepan rutz <stepan.rutz@gmx.de>
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Detoasting optionally to make Explain-Analyze less misleading
Date: Wed, 13 Sep 2023 13:09:04 +0200
Message-ID: <20230913130904.7386a230@karst> (raw)
In-Reply-To: <2f57ca27-6828-eefc-9dd3-6e2d4578a8fa@gmx.de>
References: <ca0adb0e-fa4e-c37e-1cd7-91170b18cae1@gmx.de>
<CAEze2WhXYCJ8=ZBTbRTp9rGbvju9LK6UO7hodECKWgU-_a==aw@mail.gmail.com>
<2f57ca27-6828-eefc-9dd3-6e2d4578a8fa@gmx.de>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: jgdr@dalibo.com, stepan.rutz@gmx.de, boekewurm+postgres@gmail.com
Subject: Re: Detoasting optionally to make Explain-Analyze less misleading
In-Reply-To: <20230913130904.7386a230@karst>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox