explain (verbose off, normalized) vs query planid

Hello,

as described in:
http://www.postgresql-archive.org/Re-FEATURE-PATCH-pg-stat-statements-with-plans-v02-td6015488.html

I'm wondering about the best way to build a query planid. 

It seems natural (to me) to calculate a hash value based on the normalized
plan text 
generated by

explain (costs off, normalized) 
or maybe
explain (costs off, verbose, normalized)

this normalized output can be done by adding a modified get_const_expr in
ruleutils.c as proposed in attached file.

Would this "explain normalized" feature be interesting for core team and or
users ?

Regards
PAscal

get_const_expr_normalized.c
<http://www.postgresql-archive.org/file/t348768/get_const_expr_normalized.c>  






--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html