Re: ERROR: PlaceHolderVar found where not expected
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Richard Guo <guofenglinux@gmail.com>,
PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2023-03-14T03:39:44Z
Lists: pgsql-bugs
I wrote: > WindowFuncs should be disallowed in qual clauses, so I think it's okay > to leave those flags out. An Aggref could occur in a HAVING qual though. > I'm not sure if this code could get applied to HAVING ... but it's > not immediately clear that it can't. I'd be inclined to add > PVC_RECURSE_AGGREGATES, as that seems more likely to be okay than not. Actually, on closer look: why don't we just nuke that pull_var_clause call entirely, along with the following loop inspecting its result? The subsequent loop that looks for a matching StatisticExtInfo expression will do just fine at rejecting any expression that contains Vars of the wrong relation. Maybe there is some performance argument why the pull_var_clause precheck is worth the trouble, but I'm inclined to bet that it's actually a net loss. regards, tom lane
Commits
-
Remove unnecessary code in dependency_is_compatible_expression().
- 7c509f7e5a81 14.8 landed
- 684ffac8c7d2 16.0 landed
- 3b459444301c 15.3 landed