Re: Document hashtext() and Friends?

From: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David E(dot) Wheeler" <david(at)justatheory(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Document hashtext() and Friends?
Date: 2012-02-21 20:50:36
Message-ID: CAEYLb_VzrTx9R15d=OnnJhXBvtjYBN1EyppuWnPuDS5RjQ-mnw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21 February 2012 20:30, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Geoghegan <peter(at)2ndquadrant(dot)com> writes:
>> My pg_stat_statements normalisation patch actually extends the
>> underlying hash_any() function to support 8 byte results,
>
> ... er, what?  That seems rather out of scope for that patch,
> not to mention unnecessary.

Well, assuming that you deem a uint64 query_id to be necessary, and
based on your earlier comments I take it that you do, that seemed like
the most natural way of going about getting such a value, particularly
since this change is anticipated by the comments above the function.

Of course, any further input you can give on that patch would be most
appreciated. I'm particularly eager to resolve the problems with core
infrastructure (such as that apparent bug with some Const locations),
so that we can at the very least be sure that the community won't have
to wait for the release of 9.3 at the earliest before having a
normalisation capability with stat_statements.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-02-21 20:51:07 Re: Re: [COMMITTERS] pgsql: Correctly initialise shared recoveryLastRecPtr in recovery.
Previous Message ktm@rice.edu 2012-02-21 20:30:59 Re: Document hashtext() and Friends?