| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Christofides <michael(at)pgmustard(dot)com> |
| Cc: | stepan rutz <stepan(dot)rutz(at)gmx(dot)de>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Detoasting optionally to make Explain-Analyze less misleading |
| Date: | 2024-07-08 17:08:25 |
| Message-ID: | 1080078.1720458505@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Christofides <michael(at)pgmustard(dot)com> writes:
> While looking to add support for SERIALIZE in an explain visualisation tool
> I work on, I realised there isn't yet an equivalent auto_explain parameter
> for SERIALIZE. I'm not sure if this is a deliberate omission (perhaps for a
> similar reason planning time is not included in auto_explain?), but I
> didn't see it mentioned above, so I thought best to ask in case not.
I'm not sure there's a need for it. When a query runs under
auto_explain, the output values will be sent to the client,
so those cycles should be accounted for anyway, no?
(Perhaps the auto_explain documentation should mention this?)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2024-07-08 17:32:04 | Re: Windows: openssl & gssapi dislike each other |
| Previous Message | Tom Lane | 2024-07-08 17:03:28 | Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL); |