| From: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
|---|---|
| To: | stepan rutz <stepan(dot)rutz(at)gmx(dot)de> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Detoasting optionally to make Explain-Analyze less misleading |
| Date: | 2023-09-13 11:09:04 |
| Message-ID: | 20230913130904.7386a230@karst |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Stepan & all,
On Tue, 12 Sep 2023 17:16:00 +0200
stepan rutz <stepan(dot)rutz(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2023-09-13 11:18:37 | RE: Synchronizing slots from primary to standby |
| Previous Message | Bharath Rupireddy | 2023-09-13 10:52:24 | Re: Have better wording for snapshot file reading failure |