From: legrand legrand <legrand_legrand@hotmail.com>
To: pgsql-hackers@postgresql.org
Subject: RE: [survey] New "Stable" QueryId based on normalized query text
Date: Wed, 20 Mar 2019 12:39:25 -0700 (MST)
Message-ID: <1553110765067-0.post@n3.nabble.com> (raw)
In-Reply-To: <0A3221C70F24FB45833433255569204D1FBE20A4@G01JPEXMBYT05>
References: <1553029215728-0.post@n3.nabble.com>
<0A3221C70F24FB45833433255569204D1FBE20A4@G01JPEXMBYT05>
> From: "Tsunakawa, Takayuki"
>> From: legrand legrand [mailto:legrand_legrand@]
>> There are many projects that use alternate QueryId
>> distinct from the famous pg_stat_statements jumbling algorithm.
>I'd like to welcome the standard QueryID that DBAs and extension developers
can depend on.
>Are you surveying the needs for you to develop the QueryID that can meet as
many needs as possible?
Yes, I would like first to understand what are the main needs,
then identify how it would be possible to implement it
in core, in a new extension or simply with a modified pg_stat_statements.
(I'm just a DBA not a C developer, so it will only be restricted to very
simple enhancements)
>> needs.1: stable accross different databases,
>Does this mean different database clusters, not different databases in a
single database cluster?
Same looking query should give same QueryId on any database (in the same
cluster or in distinct clusters). It can be differentiated with dbid.
>needs.5: minimal overhead to calculate
OK will add it
>needs.6: doesn't change across database server restarts
Really ? does this already occurs ?
>needs.7: same value on both the primary and standby?
I would say yes (I don't use standby) isn't this included into needs.1 ?
>> norm.9: comments aware
>Is this to distinguish queries that have different comments for optimizer
hints? If yes, I agree.
Yes and others like playing with :
set ...
select /* test 1*/ ...
set ...
select /* test 2*/ ...
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
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: legrand_legrand@hotmail.com
Subject: RE: [survey] New "Stable" QueryId based on normalized query text
In-Reply-To: <1553110765067-0.post@n3.nabble.com>
* 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