From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: invalidating cached plans |
Date: | 2005-03-15 16:53:43 |
Message-ID: | 87zmx4lujs.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Neil Conway <neilc(at)samurai(dot)com> writes:
> > (BTW, another thing to consider is how the rewriter will effect a plan's
> > dependencies: I think we should probably invalidate a plan when a
> > modification is made to a view or rule that affected the plan.
>
> This issue goes away as long as you follow the rule that any change to a
> table's schema invalidates all plans that mention the table. Views and
> tables that have rules will still be mentioned in the rangetable of the
> resulting plan, even if they aren't part of the active plan. (We use
> that for access rights checking.)
That makes me wonder. What happens if I prepare a query, then use SET SESSION
AUTHORIZATION to change my user. Then try to execute the query?
Should it recheck all the permissions? Or are all my prepared queries
credential that I'm acquiring and can use any time?
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2005-03-15 16:54:28 | Kerberos code overwrites it's own error message |
Previous Message | Shachar Shemesh | 2005-03-15 15:40:33 | Re: type unknown - how important is it? |