Remove dead code from sepgsql
Commit 4232c4b40 introduced userspace access vector cache in sepgsql, and
removed all callers of sepgsql_check_perms. Searching the usual repos for
usage in 3rd party code comes up blank. Is there any reason not to remove it
as per the attached?
--
Daniel Gustafsson https://vmware.com/
Attachments:
v1-0001-Remove-dead-code-from-sepgsql.patchapplication/octet-stream; name=v1-0001-Remove-dead-code-from-sepgsql.patch; x-unix-mode=0644Download+0-74
On Fri, Sep 2, 2022 at 5:56 AM Daniel Gustafsson <daniel@yesql.se> wrote:
Commit 4232c4b40 introduced userspace access vector cache in sepgsql, and
removed all callers of sepgsql_check_perms. Searching the usual repos for
usage in 3rd party code comes up blank. Is there any reason not to remove it
as per the attached?
Not to my knowledge.
--
Robert Haas
EDB: http://www.enterprisedb.com
On 2 Sep 2022, at 17:55, Robert Haas <robertmhaas@gmail.com> wrote:
On Fri, Sep 2, 2022 at 5:56 AM Daniel Gustafsson <daniel@yesql.se> wrote:
Commit 4232c4b40 introduced userspace access vector cache in sepgsql, and
removed all callers of sepgsql_check_perms. Searching the usual repos for
usage in 3rd party code comes up blank. Is there any reason not to remove it
as per the attached?Not to my knowledge.
Thanks for confirming, done that way.
--
Daniel Gustafsson https://vmware.com/