Subject: Re: Dump public schema ownership & seclabels
To: Noah Misch <noah@leadboat.com>
Cc: pgsql-hackers@postgresql.org
References: <20201229134924.GA1431748@rfd.leadboat.com>
 <20201230115902.GB1431748@rfd.leadboat.com>
 <ab48a34c-60f6-e388-502a-3e5fe46a2dae@postgresfriends.org>
 <20210117094102.GB1695558@rfd.leadboat.com>
From: Vik Fearing <vik@postgresfriends.org>
Message-ID: <50ebd5f1-4d61-cfda-bb19-dc41fc7dae60@postgresfriends.org>
Date: Sun, 17 Jan 2021 12:00:06 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <20210117094102.GB1695558@rfd.leadboat.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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