From: Vik Fearing <vik@postgresfriends.org>
To: Noah Misch <noah@leadboat.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Dump public schema ownership & seclabels
Date: Sun, 17 Jan 2021 12:00:06 +0100
Message-ID: <50ebd5f1-4d61-cfda-bb19-dc41fc7dae60@postgresfriends.org> (raw)
In-Reply-To: <20210117094102.GB1695558@rfd.leadboat.com>
References: <20201229134924.GA1431748@rfd.leadboat.com>
<20201230115902.GB1431748@rfd.leadboat.com>
<ab48a34c-60f6-e388-502a-3e5fe46a2dae@postgresfriends.org>
<20210117094102.GB1695558@rfd.leadboat.com>
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-c...
--
Vik Fearing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: vik@postgresfriends.org, noah@leadboat.com
Subject: Re: Dump public schema ownership & seclabels
In-Reply-To: <50ebd5f1-4d61-cfda-bb19-dc41fc7dae60@postgresfriends.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox