Re: Lock contention high - Mailing list pgsql-performance

From Peter Geoghegan
Subject Re: Lock contention high
Date
Msg-id CAH2-WzmuTpFGmFwyuBC09LmOavYcx9jqbOQOoB6ivS75m=aO_A@mail.gmail.com
Whole thread Raw
In response to Re: Lock contention high  (Jeremy Schneider <schneider@ardentperf.com>)
List pgsql-performance
On Wed, Oct 13, 2021 at 6:54 PM Jeremy Schneider
<schneider@ardentperf.com> wrote:
> only a half GB memory for autovac? (it will have a mandatory run as soon
> as you hit 200 mil XIDs, seems like you'd want the full max 1GB for it)

While anti-wraparound vacuums will become a problem for TPC-C (unless
you tune for it), it's not too sensitive to mwm. You just don't end up
accumulating too many TIDs to delete from indexes in practice, even
though the overhead from VACUUM is a concern. The new autovacuum
instrumentation in Postgres 14 makes this far clearer.

-- 
Peter Geoghegan



pgsql-performance by date:

Previous
From: Jeremy Schneider
Date:
Subject: Re: Lock contention high
Next
From: Ashkil Dighin
Date:
Subject: Re: Lock contention high