Jerry Brenner <jbrenner@xxxxxxxxxxxxx> writes: > Both Oracle and SQL Server have > consistent hash values for query plans and that makes it easy to identify > when there are multiple plans for the same query. Does that concept exist > in later releases of Postgres (and is the value stored in the json explain > plan)? No, there's no support currently for obtaining a hash value that's associated with a plan rather than an input query tree. regards, tom lane