vacuum of pg_attribute and other infrastructure tables

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

vacuum of pg_attribute and other infrastructure tables

Mark Steben-3
Good morning,

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?

Thank you,
Mark 

--
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





Reply | Threaded
Open this post in threaded view
|

Re: vacuum of pg_attribute and other infrastructure tables

Laurenz Albe
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



Reply | Threaded
Open this post in threaded view
|

Re: vacuum of pg_attribute and other infrastructure tables

Mark Steben-3
Thank you for the clarification. 

On Thu, May 2, 2019 at 12:10 PM Laurenz Albe <[hidden email]> 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