Re: Encryption of Data Specific to a Tenant in PostgreSQL database | General Idea - Mailing list pgsql-general

From Martin Ritchie
Subject Re: Encryption of Data Specific to a Tenant in PostgreSQL database | General Idea
Date
Msg-id CA+LW_6L0Gd0R41W3R0WnJJ2HC1NHXFX-rVhGSKU346qFJSv5OQ@mail.gmail.com
Whole thread Raw
In response to Re: Encryption of Data Specific to a Tenant in PostgreSQL database | General Idea  (Rob Sargent <robjsargent@gmail.com>)
List 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 by date:

Previous
From: Rob Sargent
Date:
Subject: Re: Encryption of Data Specific to a Tenant in PostgreSQL database | General Idea
Next
From: Ron
Date:
Subject: Building lots of indices in parallel