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_VCVOH9=TB0nH3XOQQ32jLijvTYY7beHMjuh+cK1oH_Hw@mail.gmail.com
Whole thread Raw
In response to Re: Hash id in pg_stat_statements  (Peter Geoghegan <peter@2ndquadrant.com>)
List pgsql-hackers
On 3 October 2012 19:54, Peter Geoghegan <peter@2ndquadrant.com> wrote:
> On 3 October 2012 19:04, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> This argument seems sensible to me.  Is there any use-case where the
>> proposed counter wouldn't do what people wished to do with an exposed
>> hash value?
>
> Yes. The hash could be used to aggregate query execution costs across
> entire WAL-based replication clusters. I'm not opposed to Daniel's
> suggestion, though.

Could we please try and reach a consensus here? If you're still dead
set against exposing the hash value, I think that just following what
Daniel has suggested is a fair compromise.

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



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Successor of MD5 authentication, let's use SCRAM
Next
From: Peter Geoghegan
Date:
Subject: Re: Hash id in pg_stat_statements