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 1hMEII-00031I-2I for pgsql-admin@arkaria.postgresql.org; Thu, 02 May 2019 16:10:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hMEIG-0005ic-6Y for pgsql-admin@arkaria.postgresql.org; Thu, 02 May 2019 16:10:44 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1hMEIF-0005hw-Sd for pgsql-admin@lists.postgresql.org; Thu, 02 May 2019 16:10:43 +0000 Received: from mx2.mailbox.org ([80.241.60.215]) by magus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hMEID-0000xi-Aq for pgsql-admin@postgresql.org; Thu, 02 May 2019 16:10:43 +0000 Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:105:465:1:2:0]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mx2.mailbox.org (Postfix) with ESMTPS id 659C7A1364; Thu, 2 May 2019 18:10:39 +0200 (CEST) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp2.mailbox.org ([80.241.60.241]) by spamfilter01.heinlein-hosting.de (spamfilter01.heinlein-hosting.de [80.241.56.115]) (amavisd-new, port 10030) with ESMTP id 0nHVxq4-zoi5; Thu, 2 May 2019 18:10:35 +0200 (CEST) Message-ID: <3e07076a17ae160c230dd3685fedc5d53f83e19d.camel@cybertec.at> Subject: Re: vacuum of pg_attribute and other infrastructure tables From: Laurenz Albe To: Mark Steben , pgsql-admin Date: Thu, 02 May 2019 18:10:33 +0200 In-Reply-To: References: Organization: Cybertec Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Mark Steben wrote: > I would like to vacuum full pg_attribute and some other postgres infrastructure tables to eliminate bloat. > Could you please confirm that the recommended method to do this is to > stop postgres, restart in single user mode, and issue the vacuum command? That is not necessary. Just run the VACUUM (FULL) as superuser. Concurrent access to pg_attribute will be blocked, which means that the database is pretty much unusable, but you don't need single user mode. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com