Re: [v9.2] Fix Leaky View Problem
| От | Robert Haas |
|---|---|
| Тема | Re: [v9.2] Fix Leaky View Problem |
| Дата | |
| Msg-id | CA+TgmoZOmyRM0hfu5EyU4n1nZQrPuAipAFxxKLdFJgeUz+4sOg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [v9.2] Fix Leaky View Problem (Kohei KaiGai <kaigai@kaigai.gr.jp>) |
| Ответы |
Re: [v9.2] Fix Leaky View Problem
|
| Список | pgsql-hackers |
On Sun, Sep 25, 2011 at 3:25 PM, Kohei KaiGai <kaigai@kaigai.gr.jp> wrote: >> I'm a bit nervous about storing security_barrier in the RTE. What >> happens to stored rules if the security_barrier option gets change >> later? >> > The rte->security_barrier is evaluated when a query referencing security > views get expanded. So, rte->security_barrier is not stored to catalog. I think it is. If you create a view that involves an RTE, the node tree is going to get stored in pg_rewrite.ev_action. And it's going to include the security_barrier attribute, because you added outfuncs support for it... No? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: