Re: Parameterized aggregate subquery (was: Pull up aggregate subquery) - Mailing list pgsql-hackers

From Yeb Havinga
Subject Re: Parameterized aggregate subquery (was: Pull up aggregate subquery)
Date
Msg-id 4E29944E.4050704@gmail.com
Whole thread Raw
In response to Re: Parameterized aggregate subquery (was: Pull up aggregate subquery)  (Hitoshi Harada <umi.tanuki@gmail.com>)
Responses Re: Parameterized aggregate subquery (was: Pull up aggregate subquery)
List pgsql-hackers
On 2011-07-22 16:17, Hitoshi Harada wrote:
>
> :(
> I updated the patch. Could you try attached once more? The "issafe"
> switch seems wrong.
Works like a charm :-). However, now there is always a copyObject of a
subquery even when the subquery is not safe for qual pushdown. The
problem with the previous issafe was that it was only assigned for
rel->baserestrictinfo != NIL. If it is assigned before the if statement,
it still works. See attached patch that avoids subquery copy for unsafe
subqueries, and also exits best_inner_subqueryscan before palloc of
differenttypes in case of unsafe queries.

regards,
--

Yeb Havinga
http://www.mgrid.net/
Mastering Medical Data


Attachment

pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Policy on pulling in code from other projects?
Next
From: Alvaro Herrera
Date:
Subject: Re: Deriving release notes from git commit messages