Re: Multitenent architecture

Поиск
Список
Период
Сортировка
От Rob Sargent
Тема Re: Multitenent architecture
Дата
Msg-id 45AB91CB-EFBF-40A6-9920-D757AA7F159D@gmail.com
обсуждение исходный текст
Ответ на Re: Multitenent architecture  (Vasu Madhineni <vasumdba1515@gmail.com>)
Ответы Re: Multitenent architecture  (Vasu Madhineni <vasumdba1515@gmail.com>)
Список pgsql-general


On Jun 5, 2020, at 2:54 AM, Vasu Madhineni <vasumdba1515@gmail.com> wrote:


If the data size is more than 6TB, which approach better?

On Fri, Jun 5, 2020 at 2:57 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Thu, 2020-06-04 at 23:52 +0800, Vasu Madhineni wrote:
> We are planning a POC on multitenant architecture in Postgres, Could you please
> help us with steps for multitenant using schema for each application model.

For few tenants, you can keep identical tables in several schemas and
set "search_path" to select a tenant.

With many tenants, you are better off with one table that holds the
data for all clients.  You can use Row Level Security to have each
tenant see only his or her data, and it might be a good idea to
use list partitioning on the tenant ID.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

The question is How many separate data owners?

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

Предыдущее
От: David Rowley
Дата:
Сообщение: Re: Possible improvement
Следующее
От: Oleksandr Shulgin
Дата:
Сообщение: Re: When to use PARTITION BY HASH?