Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE
Date
Msg-id CAKAnmm+QQP-dTkjsDVbEcphrdXqCTq-ALTCMUwPaYWZmqUp=NQ@mail.gmail.com
Whole thread Raw
In response to Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE  (Nikolay Samokhvalov <samokhvalov@gmail.com>)
List pgsql-hackers
On Wed, Nov 20, 2024 at 1:26 AM Guillaume Lelarge <guillaume@lelarge.info> wrote:
OK, but I'm not sure which example I should pick to add dirtied and written shared buffers. It looks kinda artificial. Should I choose one randomly?

It will be artificial, but I think that's ok: anyone running it on their own will be getting different numbers anyway. I was looking at the "14.1.2 EXPLAIN ANALYZE" section in perform.sgml. Here's some actual numbers I got with some playing around with concurrent updates:

         Recheck Cond: (unique1 < 10)
         Heap Blocks: exact=5
         Buffers: shared hit=2 read=5 written=4
...
 Planning:
   Buffers: shared hit=289 dirtied=9

Cheers,
Greg

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Remove useless casts to (void *)
Next
From: Greg Sabino Mullane
Date:
Subject: Re: sunsetting md5 password support