From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: vacuum vs vacuum full |
Date: | 2020-11-18 09:38:14 |
Message-ID: | 57bae976-1533-b459-145a-82f76767099b@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/18/20 2:33 AM, Atul Kumar 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:
>
> 1. What should be perform on the table Vacuum or Vacuum full ?
The documentation *clearly states* the difference between VACUUM and VACUUM
FULL.
https://www.postgresql.org/docs/9.6/sql-vacuum.html
> 2. Do we need to perform Analyze also?
I always do.
> 3. Will the operation be completed in the given time frame? how to
> check the same.
How in the heck do we know your system's hardware configuration?
> 4. Who acquire lock on table vacuum or vacuum full.
Read the docs.
> 5. If the activity goes beyond time frame, do we have any option to do
> continue doing t without acquiring lock on the table ?
>
> If you also need the structure of the table, Please let me know.
>
> Please help me by responding my query wise.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Olivier Gautherot | 2020-11-18 09:41:37 | Re: vacuum vs vacuum full |
Previous Message | Magnus Hagander | 2020-11-18 09:36:10 | Re: pg_upgrade from 12 to 13 failes with plpython2 |