For now pg_attribute bloated to 300GB in size, and we have only 260GB's of free space on disk.
In normal situation pg_attribute takes 50mb in size for our DB... Can we assume that if we will run vacuum full on pg_attribute it will take additional 50MB on disk?
Thanks
2018-03-26 16:41 GMT+03:00 Keith <keith@xxxxxxxxxxx>:
On Mon, Mar 26, 2018 at 9:35 AM, Artem Tomyuk <admin@xxxxxxxxxxxxxx> wrote:Hi, Gurus!!!!Maybe someone knows what is the best way to shrink pg_attribute in size?Maybe backup and restore of this table will sanitize "dead" records in it?Or only full vacuum can help in this situation?Thanks!VACUUM FULL would be the way to go if bloat is the issue you're trying to fix. Trying to backup up & restore a single system catalog would not be recommended.Keith
