| From: | peter plachta <pplachta(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: High QPS, random index writes and vacuum |
| Date: | 2023-04-18 02:44:47 |
| Message-ID: | CAGTqnmbpQiqoN+6btKnU_CPLdAZBbfexqJ3KWfowem9kVV2dJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmail(dot)com> wrote:
> On Tue, 18 Apr 2023 at 12:35, peter plachta <pplachta(at)gmail(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-04-18 02:49:59 | Re: High QPS, random index writes and vacuum |
| Previous Message | peter plachta | 2023-04-18 02:43:22 | Re: High QPS, random index writes and vacuum |