Re: vacuum of pg_attribute and other infrastructure tables - Mailing list pgsql-admin

From Mark Steben
Subject Re: vacuum of pg_attribute and other infrastructure tables
Date
Msg-id CADyzmyzQMDy=bB1q+Bmg6oALVkEbi6w4A8BV_yNUzYKX9tHmSg@mail.gmail.com
Whole thread Raw
In response to Re: vacuum of pg_attribute and other infrastructure tables  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-admin
Thank you for the clarification. 

On Thu, May 2, 2019 at 12:10 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
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



--
Mark Steben
 Database Administrator
@utoRevenue | Autobase 
  CRM division of Dominion Dealer Solutions 
95D Ashley Ave.
West Springfield, MA 01089

t: 413.327-3045
f: 413.383-9567

www.fb.com/DominionDealerSolutions
www.twitter.com/DominionDealer
 www.drivedominion.com





pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: vacuum of pg_attribute and other infrastructure tables
Next
From: Tom Lane
Date:
Subject: Re: Psql: could not connect to server: No such file or directory