Re: Hash id in pg_stat_statements

Peter, all,

* Peter Geoghegan (peter@2ndquadrant.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