pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feedFrom: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: Sergei Kornilov <sk@zsrv.org>
Cc: imai.yoshikazu@fujitsu.com <imai.yoshikazu@fujitsu.com>
Cc: legrand legrand <legrand_legrand@hotmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Planning counters in pg_stat_statements (using pgss_store)
Date: Sun, 25 Jul 2021 18:46:53 -0400
Message-ID: <6766.1627253213@sss.pgh.pa.us> (raw)
In-Reply-To: <84f3a8f0-2041-d4a4-4f46-ec1f99b90fb1@dunslane.net>
References: <20200329061549.smtokn3ip5pqldia@nol>
<8224bfdf-dcf8-648f-e0d8-1db1d5c215ee@oss.nttdata.com>
<20200330080359.GD79261@nol>
<1c348d6a-02e5-ef14-b9e7-22f7f36fcee1@oss.nttdata.com>
<CAOBaU_YMDofrfRrA4c_kNfFd4ZtwtoTy1XmnBom7rwyVGeFTDw@mail.gmail.com>
<8c6449d4-5fd7-f544-182b-a4bb7da1d18c@oss.nttdata.com>
<20200331060307.e7kypfynz7jous62@nol>
<ac44fd08-5923-c0f7-742d-952a6f5a14a3@oss.nttdata.com>
<20200331073321.bhnx2p63gp5px37f@nol>
<f2b4e098-1b96-e1a8-f601-a0908c9ff8c4@oss.nttdata.com>
<20200331184217.tf3x534uz4vusgmp@nol>
<bd27f039-5285-1fb7-5ed4-57f870c8a5a4@oss.nttdata.com>
<13923268-bad9-80f9-2542-5fd5e8b8c500@oss.nttdata.com>
<42557.1627229005@sss.pgh.pa.us>
<84f3a8f0-2041-d4a4-4f46-ec1f99b90fb1@dunslane.net>
Andrew Dunstan <andrew@dunslane.net> writes:
> On 7/25/21 12:03 PM, Tom Lane wrote:
>> So AFAICS this test is inherently unstable and there is no code bug
>> to be fixed. We could drop the "plans" column from this query, or
>> print something approximate like "plans > 0 AND plans <= calls".
>> Thoughts?
> Is that likely to tell us anything very useful?
The variant suggested downthread ("plans >= 2 AND plans <= calls" for the
PREPARE entry only) seems like it's still reasonably useful. At least it
can verify that a replan has occurred and been counted.
regards, tom lane
view thread (127+ messages) latest in thread
Message-ID: <6766.1627253213@sss.pgh.pa.us>
Permalink: ../6766.1627253213@sss.pgh.pa.us/
Also on: postgresql.org/message-id/6766.1627253213@sss.pgh.pa.us
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, masao.fujii@oss.nttdata.com, rjuju123@gmail.com, sk@zsrv.org, imai.yoshikazu@fujitsu.com, legrand_legrand@hotmail.com
Subject: Re: Planning counters in pg_stat_statements (using pgss_store)
In-Reply-To: <6766.1627253213@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox