> select * from foo s1; > select * from foo s2; ah, thanks for pointing this out. Not as good of a workaround as a comment since one must change aliases, but at least there is a workaround...
> As against this, there is probably also a set of people who would > *like* identical queries on identically-rowtyped tables in different > schemas to be merged. Right now they have no way to make that happen. I agree that some may want stats to merge for the same tables, and others may not. I will suggest this with some hesitation, but why not make this behavior configurable via a GUC? We recently introduced query_id_squash_values for controlling the merge of an IN list, maybe this is another queryId behavior we should provide a configuration for? -- Sami Imseih Amazon Web Services (AWS)
