From: | Vasu Madhineni <vasumdba1515(at)gmail(dot)com> |
---|---|
To: | Rob Sargent <robjsargent(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-06 03:56:55 |
Message-ID: | CAFacQoEQA+HRgk0BDHegMLmp3xNyv1GjvXNyB4tw0KiRQSd3Bg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Rob,
Our environment is medical clinical data, so each clinic as a tenant.
Approximately 500+ tenants with 6TB data.
Thank you in advance.
Regards,
Vasu Madhineni
On Fri, Jun 5, 2020 at 6:09 PM Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
>
>
> 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?
>
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2020-06-06 04:24:17 | Re: Multitenent architecture |
Previous Message | Aleš Zelený | 2020-06-05 20:57:46 | Logical replication - ERROR: could not send data to WAL stream: cannot allocate memory for input buffer |