Postgres Pro
Downloads
Home   >   mailing lists

Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)
Date
Msg-id 14734.1331668365@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)  (Peter Geoghegan <peter@2ndquadrant.com>)
Responses Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)
List pgsql-hackers
Tree view 
Peter Geoghegan <peter@2ndquadrant.com> writes:
> I probably should have exposed the query_id directly in the
> pg_stat_statements view, perhaps as "query_hash".

FWIW, I think that's a pretty bad idea; the hash seems to me to be
strictly an internal matter.  Given the sponginess of its definition
I don't really want it exposed to users.
        regards, tom lane

pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: pg_upgrade and statistics
Next
From: Dimitri Fontaine
Date:
Subject: Re: Command Triggers, patch v11