Re: Remove dead code from sepgsql

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Remove dead code from sepgsql
Date: 2022-09-02 18:52:49
Message-ID: A69F21F0-AE0B-492A-8F50-771DC761DB71@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 2 Sep 2022, at 17:55, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Fri, Sep 2, 2022 at 5:56 AM Daniel Gustafsson <daniel(at)yesql(dot)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/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-09-02 19:03:29 Re: minimum perl version
Previous Message Tom Lane 2022-09-02 18:31:57 Re: minimum perl version