Re: Restrict permissions on schema to hide pl/pgsql code

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Swanand Kshirsagar <swanandon(at)gmail(dot)com>
Cc: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Restrict permissions on schema to hide pl/pgsql code
Date: 2019-07-24 13:28:05
Message-ID: CAKFQuwasburx+UXm9Do9CFVRKFtET=US2zrYnrJcGW9aob5xrg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wednesday, July 24, 2019, Swanand Kshirsagar <swanandon(at)gmail(dot)com> wrote:
>
> Isn't revoking permissions from a schema should take care of this
> situation?
>

The pl/pgsql function body is stored in pg_catalog which the user still has
permission to read. There isn’t a good/supported way to work around this
behavior.

David J.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Peter Eisentraut 2019-07-24 13:35:04 Re: pg_locks relation cant be found in pg_class
Previous Message Swanand Kshirsagar 2019-07-24 13:03:46 Restrict permissions on schema to hide pl/pgsql code