Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gkD2S-0002Yd-Gd for pgsql-performance@arkaria.postgresql.org; Thu, 17 Jan 2019 19:09:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gkD2Q-0000vj-3w for pgsql-performance@arkaria.postgresql.org; Thu, 17 Jan 2019 19:09:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gkD2P-0000vW-KQ for pgsql-performance@lists.postgresql.org; Thu, 17 Jan 2019 19:09:13 +0000 Received: from mail-qt1-x843.google.com ([2607:f8b0:4864:20::843]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gkD2H-0006Rd-8n for pgsql-performance@lists.postgresql.org; Thu, 17 Jan 2019 19:09:11 +0000 Received: by mail-qt1-x843.google.com with SMTP id y20so12497783qtm.13 for ; Thu, 17 Jan 2019 11:09:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=jiQEbTPf3YmIc4su6So1izYRz7P+56B20ffbTmNJ3RY=; b=xdcWwz5CLwnHNqqa6/Uf5QN5S7r/BWFP8aAiB42vjjyDSdVU1y3mZuDFjircRTPqG6 5z/eeDFE3zyAHBfPfLh91Vfr+89tdTDDyWFLWL+DrL89HHuk8dK2EBbx84xvTTAz4YOW ypmzl0QPDpofH5Q7LFg5AfL/oB9f9JRMQ4zWZHPza3PM+w2g6tdEwqbwVXonMUGIRpAa jE+SYWAea8QGfhDdnjPzKFYAJMQceNDnJT0gPwmcTVCvzlSDOE9OO0UyjaufHdQ0WXi9 ez1wkEkoXYhslA/NEob6WuuZ/VKW5UgeoAYKnYroW6sNmJ4nXbVBTTS2aHsqnbrws1LJ VAlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=jiQEbTPf3YmIc4su6So1izYRz7P+56B20ffbTmNJ3RY=; b=GGNiz+JhkmbBdl40P4dvjjVTLKtRvL7nHS1LF7sVLIc2ThHIUkqRKDVS+sbuva5SFr 7LTogb7so2SQEasSAC2eKQx5ZdOkQe1LwpWq1TGv4cmCBu2aX1kw0405FzPF9hSJeLff iL0iKYRyHyrAEOYaNxbrzSaSeiSK/ysCeNuXM9VL5T5uw3Gskl0W9a1UcBry9ajU0Hld szmracxwV1f0xBSXd/4Z0Hsf/22LoUpuY1j7q06Bg39dal8jZVceSJmRgoD8TzhYX+w9 TJvarscPGX3De4YqiHm2aCEpvp+35ZPZSdwzLVKaAq4QPLC9wpvXKdoNKv3Sh9lKoeDX QSsQ== X-Gm-Message-State: AJcUukeQcIJNwSyTZsDfpo+Asrsy1jnpXB8WLhE3DHhFAuTXYWgzFDbH eMRiU3N2UWKlHtl6zerphAsgEQ== X-Google-Smtp-Source: ALg8bN79YPCC1g2bC/e1gu0/uDdHnDLZxrEGJZWN/uFdTeNK02M7hHdTTH3wsUN8Ip8P46mp4syatg== X-Received: by 2002:ac8:48c1:: with SMTP id l1mr12506758qtr.71.1547752144456; Thu, 17 Jan 2019 11:09:04 -0800 (PST) Received: from alvin.alvh.no-ip.org ([201.186.80.67]) by smtp.gmail.com with ESMTPSA id o75sm32682014qki.97.2019.01.17.11.09.03 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 17 Jan 2019 11:09:04 -0800 (PST) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id E2819876; Thu, 17 Jan 2019 16:09:01 -0300 (-03) Date: Thu, 17 Jan 2019 16:09:01 -0300 From: Alvaro Herrera To: Mariel Cherkassky Cc: pgsql-performance@lists.postgresql.org Subject: Re: autovacuum doesnt run on the pg_toast_id table Message-ID: <201901171909.eb4o7z7hikas@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20180716-1013-2c1e88 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Jan-17, Mariel Cherkassky wrote: > I did it for the original table. But I see in the logs that the autovacuun > on the toasted table isn't synced with the autovacuun of the original > table. Therefore I thought that it worth to set it also for the toasted > table. Can you explain why in the logs I see more vacuums of the original > table then the toasted table ? Should they vacuumed together ? No, they are processed separately, according to the formula explained in the documentation. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services