Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pPTFj-0003lu-O1 for pgsql-admin@arkaria.postgresql.org; Tue, 07 Feb 2023 19:03:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pPTFi-0004EV-Gc for pgsql-admin@arkaria.postgresql.org; Tue, 07 Feb 2023 19:03:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pPTFi-0004EM-5O for pgsql-admin@lists.postgresql.org; Tue, 07 Feb 2023 19:03:38 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pPTFg-0004WH-2R for pgsql-admin@postgresql.org; Tue, 07 Feb 2023 19:03:37 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 317J3VR43215332; Tue, 7 Feb 2023 14:03:31 -0500 From: Tom Lane To: Erik Serrano cc: Holger Jakobs , pgsql-admin Subject: Re: Vacuum Full not clean the table In-reply-to: References: <8aacabc6-5919-5f37-9c9a-2a3cd67adfa3@jakobs.com> Comments: In-reply-to Erik Serrano message dated "Tue, 07 Feb 2023 15:45:02 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3215330.1675796611.1@sss.pgh.pa.us> Date: Tue, 07 Feb 2023 14:03:31 -0500 Message-ID: <3215331.1675796611@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Erik Serrano writes: > For this reason, I appreciate that you can even guide me to see what is > happening or could have happened regarding the end of the process without > the expected result, which is cleaning the table. If vacuum isn't removing dead tuples, it's because there is an open transaction somewhere that can still "see" those tuples. Check for old open transactions in pg_stat_activity and pg_prepared_xacts. regards, tom lane