Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1scRfc-007Loj-2j for pgsql-general@arkaria.postgresql.org; Fri, 09 Aug 2024 15:36:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1scRfa-004B0C-Mn for pgsql-general@arkaria.postgresql.org; Fri, 09 Aug 2024 15:36:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1scRfZ-004B03-FJ for pgsql-general@lists.postgresql.org; Fri, 09 Aug 2024 15:36:46 +0000 Received: from fhigh4-smtp.messagingengine.com ([103.168.172.155]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1scRfW-003uEA-6e for pgsql-general@lists.postgresql.org; Fri, 09 Aug 2024 15:36:44 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 9237E114AB51; Fri, 9 Aug 2024 11:36:40 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 09 Aug 2024 11:36:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1723217800; x=1723304200; bh=jGxVwQyztJ5kM+tn/zsVNJy5Crj1Fv0aqTVsKfqD7EQ=; b= YCuPwKLmbqOfkUodR9d4crGc5TxduisMdwU/PFHLrjwQ/nGmx+ldC6g2MRDBEmY5 1syghmlDKb7FXVb8/92rX5iQ/dm7Sk6Zxxx2HuAMnIANGiGrr4EIoBUFeeYWr8RI sHVLL9QrCQ6Sfm4iRwjcZfJ296AwCCXAamFPS2pUqsY7pYWTFc6KpwZ08BeIzXEn 6MsRjqoAtgmmgq8yKWtmY3z+BstNySZoqgohwud19OeMZwN60OyKQCiOweWpm1wZ 7tU6FYLJ84Uh5B7lpjLefT9MUGxRNcYzNZJhx8UQR+cG7bVKVz4MpVjxGcQEp4Jc 6bhcC35/gTMgXfi6R0Jm3Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1723217800; x= 1723304200; bh=jGxVwQyztJ5kM+tn/zsVNJy5Crj1Fv0aqTVsKfqD7EQ=; b=K qUcfdx+uAUWSyodUhB8JeLAZuyr60mRlLmEPeItDGZPmm80uZOrUZuG1wyP+Qnx/ PTaG39jaMKjodnFoNGayjIbXpuEP4Z5tQqJiNR1+7Ezw2QIO5f0IzxEkIOwu7ZB2 3bk1vdkWDVckD2CZbSGheQ7COX60U96JLCqbcUNFHGk/bnIjcOaMer6DwGfM+vPU bywY/qlGGLlYMuF5XmgfD1Xds/DP40Rqm08FdADWsQ1CoXH/HWTg9h/pi1gYBFir MO3zVhbMnmEhEBCW2FIJALCZdbB+YV0GYHRAWmIa/IGo8bkn77kIDSTigaM7eDny DTVqNSo6CtEvpSpT+fiVA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrleeggdeklecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnth hsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtvdejnecu hfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrg hklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepleegveekkeekueeigfdtveei leeuhfefudefteekjeffkeejueejheegheegkedtnecuffhomhgrihhnpehpohhsthhgrh gvshhqlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhl fhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmpdhnsggprh gtphhtthhopedvpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehjvhgrnhhnshes ihhlmhdrtghomhdprhgtphhtthhopehpghhsqhhlqdhgvghnvghrrghlsehlihhsthhsrd hpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 9 Aug 2024 11:36:39 -0400 (EDT) Message-ID: Date: Fri, 9 Aug 2024 08:36:39 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Trouble understanding how to avoid/manage ERROR: multixact "members" limit exceeded To: Jim Vanns , pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 8/9/24 03:26, Jim Vanns wrote: > Hi pggen community! > > I am struggling with this error almost daily now and despite various > efforts, not succeeding in avoiding or dealing with it; > My questions are; > > 1) How should I be managing this? Although not new to PG, I am new to > this particular problem. > 2) How can I confirm what processes/tables are contributing to this > multixact "members" limit? > 3) What are the units for > vacuum_multixact_freeze_min_age/vacuum_multixact_freeze_table_age and > how should I be >     setting them appropriately for my rates etc.? I can't really find > anything that explains this clearly. > 4) How can I check that autovacuum workers are specifically able to > freeze multixact XIDs and thus avoid this? pg_stat_activity https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW wait_event_type wait_event Table 28.12. Wait Events of Type LWLock This might tell you if something is hanging up on a table or tables. > 5) Can I check if autovacuum is actually succeeding in its work pg_stat_all_tables https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ALL-TABLES-VIEW Will show you the vacuum/analyze that has been done on a table. > Jim Vanns > Principal Production Engineer > Industrial Light & Magic, London -- Adrian Klaver adrian.klaver@aklaver.com