On 9 January 2014 15:19, Tom Lane <t...@sss.pgh.pa.us> wrote: > Dean Rasheed <dean.a.rash...@gmail.com> writes: >> My first thought was that it should just preprocess any security >> barrier quals in subquery_planner() in the same way as other quals are >> preprocessed. But thinking about it further, those quals are destined >> to become the quals of subqueries in the range table, so we don't >> actually want to preprocess them at that stage --- that will happen >> later when the new subquery is planned by recursion back into >> subquery_planner(). So I think the right answer is to make >> adjust_appendrel_attrs() handle recursion into sublink subqueries. > > TBH, this sounds like doubling down on a wrong design choice.
Perhaps, but it's a design choice informed by all the problems that arose from the previous attempts. Right now I don't have any other ideas how to tackle this, so perhaps continued testing to find where this falls down will inform a better approach. If nothing else, we're collecting a useful set of test cases that the final patch will need to pass. Regards, Dean -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
