Re: why there is not VACUUM FULL CONCURRENTLY? - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: why there is not VACUUM FULL CONCURRENTLY?
Date
Msg-id CAA5RZ0v3tV-Oveanzkcg_E0GpVaJMJYAtCbSeMb-CiaghCtF7g@mail.gmail.com
Whole thread Raw
In response to Re: why there is not VACUUM FULL CONCURRENTLY?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
> > - RETABLE (it's like REINDEX, but for tables)
> > - ALTER TABLE <tab> SQUEEZE
> > - SQUEEZE <table>
> > - VACUUM (SQUEEZE)
> > - VACUUM (COMPACT)
> > - MAINTAIN <tab> COMPACT
> > - MAINTAIN <tab> SQUEEZE
> >
>
> My $0.02:
>
> COMPACT tablename ...

+1 to "COMPACT tablename"

Also the current pg_stat_progress_cluster also tracks
progress for both CLUSTER and VACUUM FULL. pg_stat_progress_vacuum
tracks progress for VACUUM. I suggest we create a new progress
view for VACUUM FULL ( or the new command agreed upon ).

Regards,

Sami



pgsql-hackers by date:

Previous
From: Mahendra Singh Thalor
Date:
Subject: Re: Non-text mode for pg_dumpall
Next
From: Tom Lane
Date:
Subject: Re: Missing quotes when deparsing XMLTABLE() and SQL/JSON query functions