On Wed, Jan 31, 2018 at 5:52 AM, Dean Rasheed <dean.a.rash...@gmail.com> wrote: > On 30 January 2018 at 16:42, Tom Lane <t...@sss.pgh.pa.us> wrote: >> So I'm thinking that (a) we do not need to check for leaky functions used >> in window support, and (b) therefore there's no need to avoid leaky >> behavior in in_range support functions. Objections? > > Yes, I concur. Since window functions can only appear in the SELECT > target list and ORDER BY clauses, they should never appear in a qual > that gets considered for push down, and thus contain_leaked_vars() > should never see a window function.
What about a query that uses window functions within a subquery? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
