Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c7ld0-0008EB-IK for pgsql-admin@arkaria.postgresql.org; Fri, 18 Nov 2016 16:03:02 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1c7lcz-0001RU-T1 for pgsql-admin@arkaria.postgresql.org; Fri, 18 Nov 2016 16:03:01 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1c7lbJ-0007gu-6g for pgsql-admin@postgresql.org; Fri, 18 Nov 2016 16:01:17 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1c7lbG-0006FX-VA for pgsql-admin@postgresql.org; Fri, 18 Nov 2016 16:01:16 +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 uAIG1CCv019338; Fri, 18 Nov 2016 11:01:12 -0500 From: Tom Lane To: rajan cc: pgsql-admin@postgresql.org Subject: Re: vacuum full is not reclaiming the space and showing non-removable rows In-reply-to: <1479470449084-5930937.post@n3.nabble.com> References: <1479470449084-5930937.post@n3.nabble.com> Comments: In-reply-to rajan message dated "Fri, 18 Nov 2016 05:00:49 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19336.1479484872.1@sss.pgh.pa.us> Date: Fri, 18 Nov 2016 11:01:12 -0500 Message-ID: <19337.1479484872@sss.pgh.pa.us> X-Pg-Spam-Score: -4.8 (----) 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 rajan writes: > We deleted(using a delete query) a lot of rows from the above table and did > a vacuum full. But we are not able to reclaim the space(occupied by this > table) and the result is showing that there are nonremovable rows. There's an old open transaction somewhere that's possibly still able to see those rows. Look for idle sessions in pg_stat_activity. I don't remember at the moment whether prepared-but-uncommitted transactions can hold back reclaiming dead data, but look into pg_prepared_xacts as well. 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