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 1gXmLt-0000fW-4U for pgsql-admin@arkaria.postgresql.org; Fri, 14 Dec 2018 12:13:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gXmLr-0000sN-QP for pgsql-admin@arkaria.postgresql.org; Fri, 14 Dec 2018 12:13:55 +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 1gXmLr-0000pt-BG for pgsql-admin@lists.postgresql.org; Fri, 14 Dec 2018 12:13:55 +0000 Received: from mail-oi1-x232.google.com ([2607:f8b0:4864:20::232]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gXmLo-0001Sc-RI for pgsql-admin@lists.postgresql.org; Fri, 14 Dec 2018 12:13:54 +0000 Received: by mail-oi1-x232.google.com with SMTP id j21so4356157oii.8 for ; Fri, 14 Dec 2018 04:13:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=zluYdepgZ/cV33OkkHNYtN4GVe62/rtuYaaVy6Hs9pQ=; b=Bt51iaB1Fq3UL12e3ytHr00beJrtV5FGoyZxz6Dwxqc9qXnLDc2A59cBXBvv5LHEJe t5t/+zHxa0OarGkfU2Gn/3mfy3uMXaMBehK3J3QG8tJEuXsucHg2SOkHilDHnwdqXkXk 4h4G6wB15uLloHuhvxoWvURmaMpUMbz/RN9kLy3ssLHl3cx1wU1P6cVhbV88DWLUk7Aq M4nfyv/jrjB60IxwV24oXBbfZ/ScwHxaHx4A47h6oRk0KwupNtpk4lYuR/rlTRXWYjlv igrjqhDt0aJDNnBtAnO/xNlPw4kWtIXvP0E44NA9y3RBWQzi3leVUL1191ksdK5+PEDs MpAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=zluYdepgZ/cV33OkkHNYtN4GVe62/rtuYaaVy6Hs9pQ=; b=JUt0ZMF6slZqQQY8dNZAAtsMzxpCc113+BVHdZEkzx7py7IgmyfoQyThp/I0RZp98V EMjICUGSlo1KT2Dw1Pr0RAL6xzDBVWaIzVv9VXKVgyMyWquSyAQxx6oHYbOnZ2I0Ka86 oR/JUHKiuF3G513BC7fvY2nERu+fEHfuGskpfDAcQPAw1whncY7Yu8Q5yLDWLhXbRBJL tXjnUWe88lN4DThiRrYUkxaaLtU+fpavT69vrX3rYHBzbjIZ+bHSzIAaTCBivcBmSgZh x3ufkWBY1ObIvhzfJBWaYFtd4VxrBM8gpqVHevy6ovIAWxg7ORA+uxn8WDMFxXLcW8RL 7ByQ== X-Gm-Message-State: AA+aEWaSU9KLf3aOWUEWhcPSwk+bfpwPAR6q4xCj+Cdw6+q9lY0wfNSw bJs7t29HUQEnQCHfRhxVA0w/VTVX X-Google-Smtp-Source: AFSGD/VE63v/z38YncI16seLpajrS5ZfWKwlTIluByH9dJz0lnkzBz6cAmQBd0kkzQgQjCeDg2s3qw== X-Received: by 2002:aca:4405:: with SMTP id r5mr1544443oia.188.1544789631672; Fri, 14 Dec 2018 04:13:51 -0800 (PST) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id a201sm2750316oii.27.2018.12.14.04.13.50 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Dec 2018 04:13:50 -0800 (PST) Subject: Re: pg_attribute getting bloated in size To: pgsql-admin@lists.postgresql.org References: <2b31f655c7696125284523fa06695429f24d79f8.camel@cybertec.at> From: Ron Message-ID: Date: Fri, 14 Dec 2018 06:13:49 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <2b31f655c7696125284523fa06695429f24d79f8.camel@cybertec.at> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 12/14/2018 05:29 AM, Laurenz Albe wrote: > Artem Tomyuk wrote: >> Why autovacuum cant delete those rows? > Either long running transactions (check pg_stat_activity) > or prepared transactions (check pg_prepared_xacts) > or stale replication slots (check pg_replication_slots). Would a manual "VACUUM FULL pg_attribute;" solve the problem? -- Angular momentum makes the world go 'round.