Re: High QPS, random index writes and vacuum - Mailing list pgsql-performance

From peter plachta
Subject Re: High QPS, random index writes and vacuum
Date
Msg-id CAGTqnmbpQiqoN+6btKnU_CPLdAZBbfexqJ3KWfowem9kVV2dJw@mail.gmail.com
Whole thread Raw
In response to Re: High QPS, random index writes and vacuum  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-performance
Thank you David -- I increased this to 1GB as well (seeing as that was the max). We are doing mostly single passes now.

On Mon, Apr 17, 2023 at 7:40 PM David Rowley <dgrowleyml@gmail.com> wrote:
On Tue, 18 Apr 2023 at 12:35, peter plachta <pplachta@gmail.com> wrote:
> I increased work_mem to 2Gb

maintenance_work_mem is the configuration option that vacuum uses to
control how much memory it'll make available for storage of dead
tuples. I believe 1GB would allow 178,956,970 tuples to be stored
before multiple passes would be required. The chunk of memory for dead
tuple storage is capped at 1GB.

David

pgsql-performance by date:

Previous
From: peter plachta
Date:
Subject: Re: High QPS, random index writes and vacuum
Next
From: Thomas Munro
Date:
Subject: Re: High QPS, random index writes and vacuum