| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adam Brightwell <adam(dot)brightwell(at)crunchydatasolutions(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Yeb Havinga <yeb(dot)havinga(at)portavita(dot)nl> |
| Subject: | Re: API change advice: Passing plan invalidation info from the rewriter into the planner? |
| Date: | 2014-06-24 21:25:15 |
| Message-ID: | 20140624212515.GZ16098@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dean,
* Dean Rasheed (dean(dot)a(dot)rasheed(at)gmail(dot)com) wrote:
> Thinking about the examples upthread, a separate issue occurs to me
> --- when defining a RLS qual, I think that there has to be a syntax to
> specify an alias for the main table, so that correlated subqueries can
> refer to it. I'm not sure if that's been mentioned in any of the
> discussions so far, but it might be quite hard to define certain quals
> without it.
Yeah, that thought had occured to me also. Have any suggestions about
how to approach that issue? The way triggers have OLD/NEW comes to mind
but I'm not sure how easily that'd work.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-06-24 22:03:29 | Re: Allowing join removals for more join types |
| Previous Message | Dean Rasheed | 2014-06-24 21:18:39 | Re: API change advice: Passing plan invalidation info from the rewriter into the planner? |