> New version of this patch prints extra statistics for all cases of
> multiple loops, not only for Nested Loop. Also I fixed the example by
> adding VERBOSE.
>
> Please don't hesitate to share any thoughts on this topic!
Thanks a lot for working on this! I really like the extra details, and
inclu
I think it *should* be enabled for planning, since that makes the default
> easier to understand and document, and it makes a user's use of "explain"
> easier.
I’d be keen to see BUFFERS off by default with EXPLAIN, and on by default
with EXPLAIN ANALYZE.
The SUMMARY flag was implemented that wa
and verbose parameters, do the
worker reported buffers numbers report what you are looking for?
i.e. explain (analyze, buffers, verbose, costs off, timing off) select *
from foo where col0 > 900 or col1 = 1;
—
Michael Christofides
Founder, pgMustard <https://pgmustard.com/>
[1]:
https://www.p
>
> So thanks again! and this will really help a lot of people.
I'd like to echo this thanks to you all.
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
> 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?
>
Yes, great point, the total duration reported by auto_explain includes it.
Explicit serialization stats might still b
024, 17)
I noticed in this thread Tom was against SERIALIZE being on by default
with ANALYZE, "because it would silently render EXPLAIN outputs from
different versions quite non-comparable." I'm not sure I agree with the
silently part, as the output from 17+ would include the serializati
> v4 patch attached
Thank you Guillaume, and nice work! I tried to see if there was anywhere
else in the documentation that would need updating, but it looks like you
covered everywhere already.
> I'm with Robert in that I've not found the buffer counts to be all that
useful most of the time.
I
> I've pushed the main patch.
Woohoo! And thank you. I've already seen quite a lot of positivity around
the commit on Twitter[1][2][3].
> I'm not planning on pushing the auto_explain.log_buffers default change
unless there's a bit more discussion about it.
Much like Guillaume, I'd also be in fav
