Re: Remove dead code from sepgsql

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Remove dead code from sepgsql
Date: 2022-09-02 15:55:51
Message-ID: CA+TgmoYGSv08O0d7qN524Ea-__AFbRUnCuV5xoP1B8ZQbG11-w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhihong Yu 2022-09-02 16:13:39 Re: On login trigger: take three
Previous Message Robert Haas 2022-09-02 15:52:38 walmethods.c/h are doing some strange things