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

Re: Hash id in pg_stat_statements

From: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hash id in pg_stat_statements
Date: 2012-10-02 19:09:35
Message-ID: CAEYLb_UQnx1+Q7+gPHyssBCpVH55niM4dfwd43zGe8_tYW5Fnw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 2 October 2012 17:58, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Right, and that's all I'm trying to address here- how do we provide a
> value for a given query which can be relied upon by outside sources,
> even in the face of a point release which changes what our internal hash
> value for a given query is.

I don't know of a way. Presumably, we'd hope to avoid this, and would
look for alternatives to anything that would necessitate bumping
PGSS_FILE_HEADER, while not going so far as to let pg_stat_statements
contort things in the core system. If I was aware of a case where this
would have come up had pg_stat_statements fingerprinting been around
at the time, perhaps I could give a better answer than that.

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


In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2012-10-02 19:14:29
Subject: Re: CREATE SCHEMA IF NOT EXISTS
Previous:From: Alvaro HerreraDate: 2012-10-02 19:08:16
Subject: Re: CREATE SCHEMA IF NOT EXISTS

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