From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
Cc: | PgHacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [sepgsql 2/3] Add db_schema:search permission checks |
Date: | 2013-04-05 13:20:12 |
Message-ID: | CA+Tgmoay0Yd7oxFfJuNEg4DQu_NStLh0fL+Sx99HZ3mu60+ajQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 4, 2013 at 8:26 AM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
> OK, I follow the manner of the terminology as we usually call it.
> The attached patch just replaced things you suggested.
Thanks, I have committed this, after making some changes to the
comments and documentation. Please review the changes and let me know
if you see any mistakes.
BTW, if it were possible to set things up so that the test_sepgsql
script could validate the version of the sepgsql-regtest policy
installed, that would eliminate a certain category of errors. I
notice also that the regression tests themselves seem to fail if you
invoke the script as contrib/sepgsql/test_sepgsql rather than
./test_sepgsql, which suggests another possible pre-validation step.
Thanks,
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2013-04-05 13:30:36 | Re: matview scannability rehash (was Re: Drastic performance loss in assert-enabled build in HEAD) |
Previous Message | Andres Freund | 2013-04-05 13:09:11 | Re: corrupt pages detected by enabling checksums |