public inbox for [email protected]
help / color / mirror / Atom feedFrom: Alvaro Herrera <[email protected]>
To: Magnus Holmgren <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: restrict_nonsystem_relation_kind led to regression (kinda)
Date: Mon, 23 Sep 2024 17:50:49 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <d71a91f41626060d0853c380cce4ddaa35cdcfd0.camel@milientsoftware.com>
Hi Magnus,
On 2024-Sep-23, Magnus Holmgren wrote:
> We've set allow_system_table_mods = on so that we could rename
> pg_database and in its place put a custom view that only lists the
> databases the current user has CONNECT privileges to. This is because
> 1) we allow customers direct (read only) access to their databases, but
> 2) we don't want them to see the other customers, and 3) restricting
> access to pg_database altogether leads to the GUIs the customers use
> spamming error messages because they expect pg_database to be readable,
> and that makes the customers (or their consultants) annoyed.
Your use case and problem seem to match bug report #18604 almost
exactly:
https://postgr.es/m/[email protected]
I suggest to read that discussion, as it contains useful information.
As I understand, you're only really safe (not just theatrically safe) by
giving each customer a separate Postgres instance.
Regards
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
view thread (3+ messages)
reply
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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: restrict_nonsystem_relation_kind led to regression (kinda)
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox