Re: Multitenent architecture

From: Rob Sargent <robjsargent(at)gmail(dot)com>
To: Vasu Madhineni <vasumdba1515(at)gmail(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general(at)postgresql(dot)org
Subject: Re: Multitenent architecture
Date: 2020-06-05 10:09:10
Message-ID: 45AB91CB-EFBF-40A6-9920-D757AA7F159D@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Jun 5, 2020, at 2:54 AM, Vasu Madhineni <vasumdba1515(at)gmail(dot)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(dot)albe(at)cybertec(dot)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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Oleksandr Shulgin 2020-06-05 10:11:54 Re: When to use PARTITION BY HASH?
Previous Message David Rowley 2020-06-05 08:13:18 Re: Possible improvement