Re: Dump public schema ownership & seclabels

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Dump public schema ownership & seclabels
Date: 2021-01-17 11:00:06
Message-ID: 50ebd5f1-4d61-cfda-bb19-dc41fc7dae60@postgresfriends.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/17/21 10:41 AM, Noah Misch wrote:
> On Sat, Jan 16, 2021 at 02:05:43PM +0100, Vik Fearing wrote:
>> On 12/30/20 12:59 PM, Noah Misch wrote:
>>> On Tue, Dec 29, 2020 at 05:49:24AM -0800, Noah Misch wrote:
>>>> https://postgr.es/m/20201031163518.GB4039133@rfd.leadboat.com gave $SUBJECT as
>>>> one of the constituent projects for changing the public schema default ACL.
>>>> This ended up being simple. Attached.
>>>
>>> This is defective; it fails to reproduce nspacl after "ALTER SCHEMA public
>>> OWNER TO pg_write_server_files; REVOKE ALL ON SCHEMA public FROM
>>> pg_write_server_files;". I will try again later.
>>
>> Could I ask you to also include COMMENTs when you try again, please?
>
> That may work. I had not expected to hear of a person changing the comment on
> schema public. To what do you change it?

It was a while ago and I don't remember because it didn't appear in the
dump so I stopped doing it. :(

Mine was an actual comment, but there are some tools out there that
(ab)use COMMENTs as crude metadata for what they do. For example:
https://postgresql-anonymizer.readthedocs.io/en/stable/declare_masking_rules/#declaring-rules-with-comments
--
Vik Fearing

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2021-01-17 11:15:29 Re: Determine parallel-safety of partition relations for Inserts
Previous Message Noah Misch 2021-01-17 09:41:02 Re: Dump public schema ownership & seclabels