From: | Avinash Kumar <avinash(dot)vallarapu(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | samhitha g <samhithagarudadri(at)gmail(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. |
Date: | 2020-05-07 20:28:21 |
Message-ID: | CAN0TujdCgR5TA4JW6T5Di6nL5RVShbUAfY+G-7Fc-ABH4U=--g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
On Thu, May 7, 2020 at 5:18 PM David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Thu, May 7, 2020 at 1:05 PM samhitha g <samhithagarudadri(at)gmail(dot)com>
> wrote:
>
>> Our application serves multiple tenants. Each tenant has the schema
>> with a few hundreds of tables and few functions.
>> We have 2000 clients so we have to create 2000 schemas in a single
>> database.
>>
>
> That is one option but I wouldn't say you must. If you cannot get
> individual tables to be multi-tenant you are probably better off having one
> database per client on a shared cluster - at least given the size of the
> schema and number of clients.
>
I am working on a similar problem.
1 database per each client may be a killer when you have a connection
pooler that creates a pool for a unique combination of (user,database).
>
> David J.
>
>
--
Regards,
Avinash Vallarapu
+1-902-221-5976
From | Date | Subject | |
---|---|---|---|
Next Message | Rory Campbell-Lange | 2020-05-07 21:08:46 | Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. |
Previous Message | David G. Johnston | 2020-05-07 20:17:35 | Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. |