Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tDmz8-003CES-BV for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Nov 2024 15:51:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tDmz6-006tAk-MD for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Nov 2024 15:51:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tDmz6-006tAc-Cs for pgsql-hackers@lists.postgresql.org; Wed, 20 Nov 2024 15:51:16 +0000 Received: from mail-io1-xd2a.google.com ([2607:f8b0:4864:20::d2a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tDmz4-002wic-AP for pgsql-hackers@postgresql.org; Wed, 20 Nov 2024 15:51:15 +0000 Received: by mail-io1-xd2a.google.com with SMTP id ca18e2360f4ac-83aad99d6bfso201796239f.0 for ; Wed, 20 Nov 2024 07:51:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732117872; x=1732722672; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ineIVYzqQpotPh1142RTgyg6KI9y2SZ3MGVp/pYm0f0=; b=PFnDSEjSrVR/kOpkW+3XhGKs2rkcNb3EVd2xHSoIyixG0TDMIFsdXpgszeYbtxRbTN igoQfMBmo9eGJaItXElixjlOlXTNYkxHfPAMskGhWLo2UBVDparl7ThXsdy9qQABZEtG N6JhMu9R0Ku7GBoehsS+/jZoXXq6Kt+BO/Z6zf/RmA4vRaZUVLuo4mKE1F2RXymm1nPx X6pu7k5+jFHUHDcvzhBEtY7ksQG1cEO2PKDuopogzhgPjtdkga8ZbFSmkilX3xhJCCKA a+ffiVfQdkC3VzT2XM107wn2Qy030T107ssRK7sX+ME300X7+iOLHxQrgU/mVbhcXIwx mVrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732117872; x=1732722672; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ineIVYzqQpotPh1142RTgyg6KI9y2SZ3MGVp/pYm0f0=; b=jbdm8dliq3nRw1hTVsJPqQ7WpYb+POXh5k2VuGqCQgVX7exXcM50NCJt5PQvtmzBMT PIc/EKWhbyJvWE/SEN7tqCmjdOmghEg0cICOLB8XiOB4A3oOqQcq5u0i+s81WtUYsnnZ edZnmxOuYq/dVHO2tcj70ro4K4Zq6e/gg6mxRGqWhSN7nOo6lAdO9BzI1LkI1WguAnOg 7YzE1YPpVuQ0wgJxIUYytJfDPUakgNTN0Reer3ELwMzipZEsaW9KjAKkmYJd+TNyHENy hjVUhgkb4ozhnKWgukkiC9rizjGzCKUtW5ywHZPQ2JIC7LvoQ2MWtx/hdQ7CX6amR02i mFPA== X-Forwarded-Encrypted: i=1; AJvYcCVP1D6xsa80bWmJ1xiBeSdwA9sSlk4+GAuZTEXdAzyvc3OhHpkyB8ohsC8piJomS0z80tL9hQHuB92UHBqr@postgresql.org X-Gm-Message-State: AOJu0YxQRdJOZdEmIsMp0G7Us474U880b+yyiDRn7PMguBBB2+IwfbIk AXkKn04wqXnlHnhELwPZ1imGiCv9OR6I6MjGRMjqfOB8/al0SaxoiPuFxJ7ozQ1+qZAqgeS6yKy XvlkknQYMsgBnQxHtMV1foMYa5MA= X-Google-Smtp-Source: AGHT+IFpc63GbhYc1nQqH4ciMhhEgs/hGbVqRuOw2xXONCBOwjBHFvIyRx/E0E+kCSt9zz5oovrXZvQmkg06ZCvE07I= X-Received: by 2002:a05:6602:1486:b0:83a:af81:f509 with SMTP id ca18e2360f4ac-83eb5fb5c66mr444796239f.4.1732117872586; Wed, 20 Nov 2024 07:51:12 -0800 (PST) MIME-Version: 1.0 References: <3076356.1730831425@sss.pgh.pa.us> In-Reply-To: From: Greg Sabino Mullane Date: Wed, 20 Nov 2024 10:50:36 -0500 Message-ID: Subject: Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE To: Guillaume Lelarge Cc: Robert Haas , Michael Christofides , David Rowley , "David G. Johnston" , Nikolay Samokhvalov , Tom Lane , pgsql-hackers@postgresql.org Content-Type: multipart/alternative; boundary="0000000000008139d006275a1e26" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008139d006275a1e26 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Nov 20, 2024 at 1:26=E2=80=AFAM Guillaume Lelarge 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=3D5 > Buffers: shared hit=3D2 read=3D5 written=3D4 ... > Planning: > Buffers: shared hit=3D289 dirtied=3D9 Cheers, Greg --0000000000008139d006275a1e26 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Nov 20, 2024 at 1:26=E2=80=AFAM G= uillaume Lelarge <guillaume@le= large.info> wrote:
OK, but I'm not sure which exam= ple 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=C2=A0it on their own will be getting different numbers anyway. I wa= s looking at the "14.1.2 EXPLAIN ANALYZE" section in perform.sgml= . Here's some actual numbers I got with some playing around=C2=A0with c= oncurrent updates:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Recheck Cond: (unique1 <= 10)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Heap Blocks: exact=3D5
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0Buffers: shared hit=3D2 read=3D5 written=3D4
...
= =C2=A0Planning:
=C2=A0 =C2=A0Buffers: shared hit=3D289 dirtied=3D9

Cheers,
Greg

--0000000000008139d006275a1e26--