From: | Vasu Madhineni <vasumdba1515(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Multitenent architecture |
Date: | 2020-06-05 07:48:52 |
Message-ID: | CAFacQoETZGA7e6WOwgz6Q9vFd=T1xkLVuLW0DP_40h+Ty7ca6g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2020-06-05 08:13:18 | Re: Possible improvement |
Previous Message | Laurenz Albe | 2020-06-05 06:57:09 | Re: Multitenent architecture |