Sami Imseih <samimseih@gmail.com> writes:
> 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?
I don't like that GUC and I would not like this one either. We
learned years ago that GUCs that change query semantics are a bad
idea, but apparently now we have hackers who need to relearn that
lesson the hard way. (Admittedly, this isn't quite *query* semantics,
which perhaps lessens the blast radius. But I think we're still going
to regret query_id_squash_values.)
regards, tom lane
