Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ay37h-0003pF-1x for pgsql-admin@arkaria.postgresql.org; Wed, 04 May 2016 20:10:17 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ay37g-0007Fn-CE for pgsql-admin@arkaria.postgresql.org; Wed, 04 May 2016 20:10:16 +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 1ay35z-0005Bn-Bm for pgsql-admin@postgresql.org; Wed, 04 May 2016 20:08:31 +0000 Received: from mail-wm0-x235.google.com ([2a00:1450:400c:c09::235]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1ay35w-00007d-Lq for pgsql-admin@postgresql.org; Wed, 04 May 2016 20:08:30 +0000 Received: by mail-wm0-x235.google.com with SMTP id n129so203312062wmn.1 for ; Wed, 04 May 2016 13:08:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=flexibee-eu.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=///XPv+5ur1/V+Lvs0A1SLI6F93hg3w6r3GwNqEozYM=; b=QrCUbZh0AA5is+ccRBDBzX3NHthf2aiDgppTQODw+5BfFHAjIj2dbTLLVMBNm5Jr6s dCksMv+WL5xbVDWd+ZOcMpG3IZxf4YU/KTvXwpBlflGHx82DlYge+nQO8qBt7fqjAUWQ D2sDYC/xELlgKslQY5zv6Vxe+aZcc7SlRMCBAV6GRjf6oInfGv/lDUPQt8eu5ZrN3HDk rc/McpmiCgowLiF/fxu/kgJK9wWT7TMNlnEh+6z50gfzZKx4ox5l+Q4kqyPo/qtbNUzg hQtrNaYc5ywlyXuyLl6XnHzHWLEVFt0CrDHB2gXYzZEaKPglGwsfzlwZNZ4dJ/HE40UC Vrkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=///XPv+5ur1/V+Lvs0A1SLI6F93hg3w6r3GwNqEozYM=; b=chJA3ml/jHe4KYUkHKRX2YI2M9OZie0GG0tabT7uXdFlmm7P5+U2p0+rbyw4XNqWY9 Be0Uuns4zmKljiFR2HNSFZQv+AZ78pDl6OMPHfgeMQXx8G2VscbTKI1Wpd5cmAWHDEzE gsuF4E9iFOoo4lkkrC3hn++OnLVnp57jiD22BRTRFsXFrRc+Vfa+mX8MGWj/fl5seOZ2 wFq4BDNHRtHmJ0LzH7T+3YeGqNVN0p8ZkvCrmi2RlaU2aj92JOwlTs8Lf5AzSo7Od476 gT0+mNHuaHNb3WURVfIqrJLCG34JaXSujPO6r6SIgvD/tfSWNyKQ4zoTrwQq2dDmkhlG q4pw== X-Gm-Message-State: AOPr4FUlaWPy4kBHLhF3Q4Z5Qf8opvijryBnUTu4y0IINq2PQo5tYNKay8M2KkyZkh1r48Qz X-Received: by 10.28.167.193 with SMTP id q184mr11515866wme.63.1462392507533; Wed, 04 May 2016 13:08:27 -0700 (PDT) Received: from osvetlik.home ([77.48.30.240]) by smtp.gmail.com with ESMTPSA id jh2sm5989635wjb.39.2016.05.04.13.08.26 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 04 May 2016 13:08:26 -0700 (PDT) Subject: Re: Autovacuum of pg_shdepend To: pgsql-admin@postgresql.org References: <572A1072.5080308@flexibee.eu> From: =?UTF-8?B?T25kxZllaiBTdsSbdGzDrWs=?= Message-ID: <572A56B9.1020202@flexibee.eu> Date: Wed, 4 May 2016 22:08:25 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.6 (--) 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 Dne 4.5.2016 v 20:52 Victor Yegorov napsal(a): > 2016-05-04 18:08 GMT+03:00 Ondřej Světlík >: > > we have a strange problem with autovacuum. We have three workers, > but usually only one works and two are waiting as they are all > trying to process table pg_shdepend which is shared between all > databases. > > > I hit the same issue when we've migrated out all large objects (~200Gb > total), I've executed `vacuumlo` and then all autovacuums started to > process `pg_shdepend`. > They've been picking on this table over and over again from different > databases, but were stopping on the truncation phase due to other > autovacuums were waiting on the same table. > > I ended up manually vacuuming this table in the database, that was > cleaned up, and also in the `postgres` DB. It fixed the case for me. > This was on 9.0.23 though. > > -- > Victor Y. Yegorov Thank you very much, we have a working autovacuum on one of our clusters again. That's awesome :-). Ondřej -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin