Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ay2Ac-0000Fp-ME for pgsql-admin@arkaria.postgresql.org; Wed, 04 May 2016 19:09:14 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ay2Ab-0008Va-PH for pgsql-admin@arkaria.postgresql.org; Wed, 04 May 2016 19:09:13 +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 1ay2Ab-0008VC-5W for pgsql-admin@postgresql.org; Wed, 04 May 2016 19:09:13 +0000 Received: from mail-wm0-x234.google.com ([2a00:1450:400c:c09::234]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1ay2AY-0007Gj-FG for pgsql-admin@postgresql.org; Wed, 04 May 2016 19:09:12 +0000 Received: by mail-wm0-x234.google.com with SMTP id a17so110957051wme.0 for ; Wed, 04 May 2016 12:09:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=flexibee-eu.20150623.gappssmtp.com; s=20150623; h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=zw/WZXzU2qqMoBjceeMuO6y2k5Rg6elbJIax9pHb53w=; b=bBcs31hntvuSIlCrQG1L5tfSeaqnc5EDnIrVrlCBPtAOt7r/g1xutyPe3nHNEsXOxi lzFL9eUVnyDvEUmEV8Mp5uhUPUifXep6qfi/VaGzWun0/ZqloFTn4KzclS3mJfrS3L7O Luc+CsziJKx78B2W0MZmLu6MaRKvw7+V+rAty4N4FS/To/3D+1wCerIihU7feaFhylZD PrvE5aLMN21Vr6rrKrtrh2KhyeoU88bF3sVpue20MRh98ygB6dXsQAmXAju4vv9s0PEw LqFQ6zmiL0M8DQMzV4GDPb5dNUSn0Rg2TZN8xIUZfmk1JdMldR5ofLFIFKXE4+5Vauaf jZ+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=zw/WZXzU2qqMoBjceeMuO6y2k5Rg6elbJIax9pHb53w=; b=YUBBXafxdi9Xkh1xlewdC+AvP3ymLWjTWz7M841bTGKx064CHWj6zTglaKSyfFbN06 E6qjk0DF1EP4cZ652LE4n8rs8r8Km4VBYHYFlqDgKJQjXgTnyc/jiBg5QkGRKK/U7fpl uVWpSx1FHbnWqE0avDrqgHqrNxgoKfIZcUs386iNoWbeJrYhTLb6yYF3KdmkFdvf8Pkg o9ym60pY1mN8rYBbFpQ+qniWPFytzkogN4/e2QkDRZXvFenitnZ6Yzt2Rofioo8t6xmE TzMeHGn16iHZ6jYmWL1AtDwe8wIi9s2LECDZv2dd9mP+6xld/AaXo7iZBWx8Dm90h4KH lxbw== X-Gm-Message-State: AOPr4FVc9aabmqKOAg0zUXaEqNNoZ35hUK4s7e1cpdpZhkgGYyLmgDtoOZgjrbNBYies7lk1 X-Received: by 10.28.25.69 with SMTP id 66mr10503807wmz.39.1462388949030; Wed, 04 May 2016 12:09:09 -0700 (PDT) Received: from osvetlik.home ([77.48.30.240]) by smtp.gmail.com with ESMTPSA id y70sm5872537wmd.3.2016.05.04.12.09.08 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 04 May 2016 12:09:08 -0700 (PDT) From: =?UTF-8?B?T25kxZllaiBTdsSbdGzDrWs=?= Subject: Re: Autovacuum of pg_shdepend To: pgsql-admin@postgresql.org References: <20160504152518.GA102195@alvherre.pgsql> Message-ID: <572A48D3.9040906@flexibee.eu> Date: Wed, 4 May 2016 21:09:07 +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: <20160504152518.GA102195@alvherre.pgsql> 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 17:25 Alvaro Herrera napsal(a): > Ondřej Světlík wrote: >> Hello, >> >> 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. > > Ooh, interesting bug. > > As a workaround I suggest connecting to all of your databases except one > and disabling autovacuum for pg_shdepend. Then the table will be > processed in the one database where you left it enabled, and the other > workers will take care of the rest of the tables. > > I'll think about a real fix. > Thank you, Alvaro, we have already tried this, but we are not permitted to alter system tables. Changing allow_system_table_mods doesn't seem safe enough, is there another way to achieve this? Oh, I forgot to mention this is 9.4.7. Thanks, 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