Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cQw6Q-0007bw-SJ for pgsql-admin@arkaria.postgresql.org; Tue, 10 Jan 2017 13:04:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cQw6Q-0001xP-Dc for pgsql-admin@arkaria.postgresql.org; Tue, 10 Jan 2017 13:04:38 +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 1cQw6P-0001wn-DQ for pgsql-admin@postgresql.org; Tue, 10 Jan 2017 13:04:37 +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 1cQw6I-0001KU-Dm for pgsql-admin@postgresql.org; Tue, 10 Jan 2017 13:04:36 +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 v0AD4SBC030626; Tue, 10 Jan 2017 08:04:28 -0500 From: Tom Lane To: gleeco cc: pgsql-admin@postgresql.org Subject: Re: vacuum toast loop? In-reply-to: References: Comments: In-reply-to gleeco message dated "Tue, 10 Jan 2017 00:53:06 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <30624.1484053468.1@sss.pgh.pa.us> Date: Tue, 10 Jan 2017 08:04:28 -0500 Message-ID: <30625.1484053468@sss.pgh.pa.us> X-Pg-Spam-Score: -5.1 (-----) 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 gleeco writes: > hello - i've a long-running manual vacuum on a big size table. It's many > TB db that has some toast. What is odd is that it keeps looping back on > the same toast / index, eg. It's not looping ... it's filling up your maintenance_work_mem (which is evidently set to 1GB) with dead TIDs and then pausing to do a cycle of index cleaning. You have evidently let that table get, um, severely bloated. Was autovacuum off? 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