autovacuum_naptime being only 5 seconds seems too frequent. A lock_timeout
might be 1-5 seconds depending on your system. Usually, DDL can fail and
wait a little time rather than lock the table for minutes and have all
reads back up behind the DDL.
Given you have autovacuum_vacuum_cost_limit set
On Thu, May 7, 2020 at 5:17 PM Avinash Kumar
wrote:
> Hi,
>
> On Thu, May 7, 2020 at 6:08 PM Rory Campbell-Lange <
> r...@campbell-lange.net> wrote:
>
>> One of our clusters has well over 500 databases fronted by pg_bouncer.
>>
>> We get excellent connection "flattening" using pg_bouncer with
>>
On Thu, May 7, 2020 at 4:05 PM samhitha g
wrote:
> Hi experts,
>
> 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.
>
> While doing this, i
Hi,
On Fri, May 8, 2020 at 3:53 AM Laurenz Albe
wrote:
> On Fri, 2020-05-08 at 03:47 -0300, Avinash Kumar wrote:
> > > Just set "autovacuum_max_workers" higher.
> >
> > No, that wouldn't help. If you just increase autovacuum_max_workers, the
> total cost limit of
> >
On Fri, 2020-05-08 at 03:47 -0300, Avinash Kumar wrote:
> > Just set "autovacuum_max_workers" higher.
>
> No, that wouldn't help. If you just increase autovacuum_max_workers, the
> total cost limit of
> autovacuum_vacuum_cost_limit (or vacuum_cost_limit) is shared by so many
> workers and it
>
Hi,
On Fri, May 8, 2020 at 3:31 AM Laurenz Albe
wrote:
> 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
>
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
On Thu, May 7, 2020 at 11:04 PM David Rowley wrote:
> On Fri, 8 May 2020 at 13:51, github kran wrote:
> > I can't either DROP or ALTER any other tables ( REMOVE Inheritance
> for any of old tables where the WRITES are not getting written to). Any of
> the ALTER TABLE OR DROP TABLE DDL's
Thanks David for your replies.
On Thu, May 7, 2020 at 11:01 PM David Rowley wrote:
> On Fri, 8 May 2020 at 09:18, github kran wrote:
> > 1) We haven't changed anything related to autovacuum except a work_mem
> parameter which was increased to 4 GB which I believe is not related to
>
