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

Re: Hash id in pg_stat_statements

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
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-01 16:12:41
Message-ID: 20121001161241.GV1267@tamriel.snowman.net (view raw or flat)
Thread:
Lists: pgsql-hackers
Peter, all,

* Peter Geoghegan (peter(at)2ndquadrant(dot)com) wrote:
> Well, I'll point out once again that the argument about its stability
> is invalid, because we serialise the entries to disk. If a point
> release changes the representation of the query tree such that the
> hash values won't match, then we have no recourse but to bump
> pg_stat_statements version number, and invalidate all existing
> entries.

What if we simply included the pg_stat_statements version number in
what's shown to the user as the 'hash'?  ver#.hash ?

	Thanks,

		Stephen

In response to

Responses

pgsql-hackers by date

Next:From: Peter GeogheganDate: 2012-10-01 16:18:52
Subject: Re: Hash id in pg_stat_statements
Previous:From: Stephen FrostDate: 2012-10-01 16:06:19
Subject: Re: CTE optimization fence on the todo list?

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