Re: Hash id in pg_stat_statements - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Hash id in pg_stat_statements
Date
Msg-id CAEYLb_U1rwGJWiy92pD=x+7ZFNju0nB91-WkDY-OAV9uvxPmeQ@mail.gmail.com
Whole thread Raw
In response to Re: Hash id in pg_stat_statements  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Hash id in pg_stat_statements  (Daniel Farina <daniel@heroku.com>)
List pgsql-hackers
On 3 October 2012 19:04, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Daniel Farina <daniel@heroku.com> writes:
>> Instead, I think it makes sense to assign a number -- arbitrarily, but
>> uniquely -- to the generation of a new row in pg_stat_statements, and,
>> on the flip side, whenever a row is retired its number should be
>> eliminated, practically, for-ever.  This way re-introductions between
>> two samplings of pg_stat_statements cannot be confused for a
>> contiguously maintained statistic on a query.
>
> This argument seems sensible to me.

Daniel: Could you please submit the patch that you were working on
that does this to the next commitfest?

-- 
Peter Geoghegan       http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services



pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Truncate if exists
Next
From: Dimitri Fontaine
Date:
Subject: Re: Deparsing DDL command strings