| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Greg Smith <greg(dot)smith(at)crunchydatasolutions(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Subject: | Re: Prohibit row-security + inheritance in 9.4? |
| Date: | 2014-01-30 17:18:13 |
| Message-ID: | CA+TgmoYwTAgiSh9sgddyZZ8GoPT9rVZDHLVWUZ8NQNSRO8Ovyg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 30, 2014 at 2:39 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> Earlier discussions seemed to settle on each relation having its own
> row-security quals applied independently. So quals on a parent rel did
> not cascade down to child rels.
Do you have a link to that prior discussion? I don't remember
reaching consensus specifically on that point. And at any rate, if
the implementation complexity mitigates strongly in the other
direction, that may be a sign that we should consider revising our
opinion on what the right thing to do is.
The problem with just accepting that feature A doesn't work with
feature B and releasing anyway is that, in many cases, nobody ever
gets around to fixing it. We have some of those warts already, and
I'm not keen to add more.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-01-30 17:23:41 | Re: Add min and max execute statement time in pg_stat_statement |
| Previous Message | Tom Lane | 2014-01-30 16:50:47 | Re: Add min and max execute statement time in pg_stat_statement |