Comments on: PostgreSQL: Execute VACUUM FULL without Disk Space

By: lee r

lee r — Fri, 28 Jun 2019 04:09:25 +0000

Or … alloc that new TS permanently for that large table, hopefully on some fast media, or better yet, a separate channel, & include it in the backup plan.

By: Anvesh Patel

Anvesh Patel — Fri, 07 Sep 2018 11:37:20 +0000

In reply to Karthikeyan. Nice question, Here, we need probably because it requires to update FSM value. But still, I am not sure and need to check PostgreSQL internal.

By: Karthikeyan

Karthikeyan — Thu, 06 Sep 2018 18:14:41 +0000

I have a question. When we move the table to another tablespace, Internally It should clear the fragmentation. In this case why should we do vacum full on the table. I am asking the question based on my oracle exp.

By: Jasen

Jasen — Thu, 09 Aug 2018 06:43:30 +0000

much cleaner that what I was planning to do.

By: Anvesh Patel

Anvesh Patel — Sat, 20 Aug 2016 07:41:13 +0000

In reply to Felipe. Thanks Felipe,

By: Felipe

Felipe — Fri, 19 Aug 2016 17:16:16 +0000

I had passed throught a situation exactly like that, a table became to big, back then I didn´t what to do, well, I end up increasing the disk where the database is allocated and THEN I executed the vaccum. Your way is better and technical.

By: jenny

jenny — Sun, 06 Dec 2015 17:25:46 +0000

I am regular visitor, how are you everybody? Thiis post posted at this
web page is truly pleasant.