Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Avinash Kumar <avinash(dot)vallarapu(at)gmail(dot)com>, Rory Campbell-Lange <rory(at)campbell-lange(dot)net>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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-08 06:31:14
Message-ID: 17c5b15451fac2ace7a815d1d2c8f86e1d232802.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, 2020-05-07 at 18:17 -0300, Avinash Kumar wrote:
> > The nice thing about separate databases is that it is easy to scale
> > horizontally.
>
> Agreed. But, how about autovacuum ? Workers shift from DB to DB and 500 clusters
> means you may have to have a lot of manual vacuuming in place as well.

Just set "autovacuum_max_workers" higher.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Avinash Kumar 2020-05-08 06:47:06 Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
Previous Message github kran 2020-05-08 06:17:17 Re: AutoVacuum and growing transaction XID's