Re: pg_attribute, pg_class, pg_depend grow huge in count and sizewith multiple tenants. - Mailing list pgsql-performance

From David G. Johnston
Subject Re: pg_attribute, pg_class, pg_depend grow huge in count and sizewith multiple tenants.
Date
Msg-id CAKFQuwafqFBr+jJ9fGie19CCDoBiGarJejhcwiYHaYyM+kY_kQ@mail.gmail.com
Whole thread Raw
In response to pg_attribute, pg_class, pg_depend grow huge in count and size withmultiple tenants.  (samhitha g <samhithagarudadri@gmail.com>)
Responses Re: pg_attribute, pg_class, pg_depend grow huge in count and sizewith multiple tenants.  (Avinash Kumar <avinash.vallarapu@gmail.com>)
List pgsql-performance
On Thu, May 7, 2020 at 1:05 PM samhitha g <samhithagarudadri@gmail.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.

David J.

pgsql-performance by date:

Previous
From: Virendra Kumar
Date:
Subject: Re: Explain plan changes - IN CLAUSE ( Passing direct values VsINNER Query )
Next
From: Avinash Kumar
Date:
Subject: Re: pg_attribute, pg_class, pg_depend grow huge in count and sizewith multiple tenants.