Skip site navigation (1) Skip section navigation (2)

Re: Hash id in pg_stat_statements

From: Euler Taveira <euler(at)timbira(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hash id in pg_stat_statements
Date: 2012-10-01 15:02:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 01-10-2012 11:22, Magnus Hagander wrote:
> As long as we *tell* them under what conditions it might change, I
> think it's perfectly fine. Particularly those who are likely to use
> this functionality should certainly be capable of understanding that.
Even if we do that it is too much work for those statistics tools, isn't it?
Instead of relying on internal structures hash, why don't you expose the query
text hash to such tools? If you solve the space normalizations, it is an
almost perfect solution for your use case.

   Euler Taveira de Oliveira - Timbira
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2012-10-01 15:06:12
Subject: Re: BUG #7534: walreceiver takes long time to detect n/w breakdown
Previous:From: Tom LaneDate: 2012-10-01 15:00:35
Subject: Re: pg_malloc() versus malloc(0)

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group