Ashhar Hasan

FYI @raunaqmorarka @sopel39

One practical way this config is used to prevent people from running queries which scan too many partitions (to prevent costs and to force users to add predicates on partition...

some concerns about the larger direction @brandboat. We have experimental toggle in Postgresql already. It's experimental because it degrades performance for queries with equality conditions (because = without COLLATE can...

@vlad-lyutenko Exactly correct understanding. > this PR will not resolve problem, but just postpone it until times when users will have more difficult column name, which will conflict with our...

> I more think about solution of providing users with more detailed description what happens and how to resolve problem, using custom prefix. This I agree with - see https://github.com/trinodb/trino/pull/14224#discussion_r976109333

I think the current solution is the best we can do for now while also not breaking user queries. An alternative might be to expose these columns using prefixes which...

LGTM % remaining comments. Please let me know when addressed @ssheikin

@derek-pyne I've been travelling so did not get a chance to re-review/merge. I'll get to this starting the weekend/Monday. Sorry about the long wait.

@cla-bot check

Squashed the commits. Will merge once CI is done. Thanks for the fix.