Remove dead code from sepgsql

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Remove dead code from sepgsql
Date: 2022-09-02 09:56:31
Message-ID: 3BD5C3BF-FECA-4496-AE53-5E447997AA0B@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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/

Attachment Content-Type Size
v1-0001-Remove-dead-code-from-sepgsql.patch application/octet-stream 3.1 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Erik Rijkers 2022-09-02 10:01:09 Re: Clarify restriction on partitioned tables primary key / unique indexes
Previous Message David Rowley 2022-09-02 09:44:08 Clarify restriction on partitioned tables primary key / unique indexes