pg_multixact/members growing - Mailing list pgsql-general

From Tiffany Thang
Subject pg_multixact/members growing
Date
Msg-id CAB_W-NPMuRdAtGapGuorT4y6jUtCWndqMJHqKaw4FcypPhKGXQ@mail.gmail.com
Whole thread Raw
Responses Re: pg_multixact/members growing  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi,
Our pg_multixact/members directory has been growing to more than 18GB over the last couple of months. According to the documentation, the files in there are used to support row locking by multiple transactions and when all tables in all databases are eventually scanned by VACUUM, the older multixacts are removed. In our case, the files are not removed. Any suggestions what I should do to purge the files automatically? Can old files since the last reboot be manually removed? 

PG version: 9.6.8

autovacuum_multixact_freeze_max_age is the default 400000000. After reading the documentation, I'm still not clear what this parameter does and if it should be adjusted. Can someone explain?

Thanks.

pgsql-general by date:

Previous
From: Maxim Boguk
Date:
Subject: Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
Next
From: Andres Freund
Date:
Subject: Re: found xmin from before relfrozenxid on pg_catalog.pg_authid