Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e9eny-0002gU-R5 for pgsql-admin@arkaria.postgresql.org; Tue, 31 Oct 2017 22:14:42 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e9enx-0003x1-BD for pgsql-admin@arkaria.postgresql.org; Tue, 31 Oct 2017 22:14:41 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e9emA-0000g0-4C for pgsql-admin@postgresql.org; Tue, 31 Oct 2017 22:12:50 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e9em2-00008T-OD for pgsql-admin@postgresql.org; Tue, 31 Oct 2017 22:12:49 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v9VMCdvr029090; Tue, 31 Oct 2017 18:12:39 -0400 From: Tom Lane To: Arjun Ranade cc: pgsql-admin@postgresql.org Subject: Re: Missing Chunk Error when doing a VACUUM FULL operation - DB Corruption? In-reply-to: References: <13631.1509479942@sss.pgh.pa.us> <23996.1509486974@sss.pgh.pa.us> Comments: In-reply-to Arjun Ranade message dated "Tue, 31 Oct 2017 18:08:20 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29088.1509487959.1@sss.pgh.pa.us> Date: Tue, 31 Oct 2017 18:12:39 -0400 Message-ID: <29089.1509487959@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Arjun Ranade writes: > There is nothing in pg_prepared_xacts, however, in pg_stat_activity there > are two pglogical processes that have a "backend_start" of "2017-06-17" > when the last time we restarted this server. Both are not waiting and have > null for "state." This might be expected behavior for pglogical. I don't know much about pglogical, but if it's holding back the xmin horizon (as it appears to be doing) that is a really bad pglogical bug. If you try vacuum verbose (doesn't have to be FULL) on some table that gets lots of update traffic, does it report a large number of dead-but- not-removable rows? > I did try TRUNCATE before but even as the postgres user, but for some > reason it didn't allow me to truncate because it was a system table. Mmm. You could get around that, but possibly not without restarting in single-user mode, which is probably more interruption in service than you want. It might be easier to force-quit the pglogical sessions. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin