Re: vacuum vs vacuum full - Mailing list pgsql-general

From Olivier Gautherot
Subject Re: vacuum vs vacuum full
Date
Msg-id CAJ7S9TWG_PD2YfBH3hQPT8Cww60LC8snXUjvqrh6b2LOe2XQTA@mail.gmail.com
Whole thread Raw
In response to Re: vacuum vs vacuum full  (Ron <ronljohnsonjr@gmail.com>)
List pgsql-general

On Wed, Nov 18, 2020 at 10:45 AM Ron <ronljohnsonjr@gmail.com> wrote:
On 11/18/20 3:41 AM, Olivier Gautherot wrote:
Hi Atul,

On Wed, Nov 18, 2020 at 9:33 AM Atul Kumar <akumar14871@gmail.com> wrote:
Hi,

We have a table of 3113GB, and we are planning to vacuum it in non
business hours i.e. 12AM to 4AM, So my queries are:
[snip]
 
3. Will the operation be completed in the given time frame? how to
check the same.

Given the size of the table, it will probably take several days.

No matter how long it takes, this is an excellent argument for partitioning Very Large Tables: many maintenance tasks are made much easier.

I can only agree with this comment. The main issue I see is the available disk space, as the partitioning process will include copying the whole table. 

Libre de virus. www.avast.com

pgsql-general by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: vacuum vs vacuum full
Next
From: Marcin Giedz
Date:
Subject: Re: pg_upgrade from 12 to 13 failes with plpython2