Re: Encryption of Data Specific to a Tenant in PostgreSQL database | General Idea

Поиск
Список
Период
Сортировка
От Martin Ritchie
Тема Re: Encryption of Data Specific to a Tenant in PostgreSQL database | General Idea
Дата
Msg-id CA+LW_6L0Gd0R41W3R0WnJJ2HC1NHXFX-rVhGSKU346qFJSv5OQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Encryption of Data Specific to a Tenant in PostgreSQL database | General Idea  (Rob Sargent <robjsargent@gmail.com>)
Список pgsql-general
Дерево обсуждения
I have had good luck with security barrier views and performance. The main thing security barrier does is ensure that where statements are processed correctly.

The big consideration IMHO is how many tenants are you dealing with. A couple of tenants, then best to give them separate databases. More than a couple, but less than 50 or so, then best to give them all separate schemas. If there are thousands of tenants (like an internet application) then security barrier views are usually the easiest option to manage.

Martin Ritchie
Geotab
Senior DBA
Direct+1 (519) 741-7660
Toll-free+1 (877) 436-8221
Visitwww.geotab.com
Twitter | Facebook | YouTube | LinkedIn


On Thu, Feb 11, 2021 at 9:33 PM Rob Sargent <robjsargent@gmail.com> wrote:
DBA=~super user
If your clients have dba privs you need separate (vertical)servers


В списке pgsql-general по дате отправления:

Предыдущее
От: Rob Sargent
Дата:
Сообщение: Re: Encryption of Data Specific to a Tenant in PostgreSQL database | General Idea
Следующее
От: Ron
Дата:
Сообщение: Building lots of indices in parallel