Re: vacuum vs vacuum full

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Atul Kumar <akumar14871(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: vacuum vs vacuum full
Date: 2020-11-18 15:11:37
Message-ID: CAKFQuwZNL0PsVYYW=2FU6FP4a4r4u1jddz64TXcbOGEPSf+iQg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 18, 2020 at 1:33 AM Atul Kumar <akumar14871(at)gmail(dot)com> wrote:

> Hi,
>
> We have a table of 3113GB, and we are planning to vacuum it in non
>

Just making sure that isn't a typo (repeated 1s)...

business hours i.e. 12AM to 4AM, So my queries are:
>
> 1. What should be perform on the table Vacuum or Vacuum full ?
>

You should be vacuuming that table constantly, so why is the particular
vacuum special? What are the "last vacuum" related statistics for this
table?

There is "vacuum" and there is "rebuilding the whole table from scratch",
the later of which is unfortunately named "vacuum full".

If you haven't started learning/thinking about it yet you should try and
get an understanding around where your system is in the process of
requiring an anti-wraparound vacuum. Or, more generally, using "vacuum
freeze".

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Snjezana Frketic 2020-11-18 16:00:07 Re: How to select values in a JSON type of column?
Previous Message Paul Förster 2020-11-18 14:59:30 Re: vacuum vs vacuum full