Re: Is it ok to run vacuum full verbose command for live database for the tables which has more dead tuples?

From: Fabio Pardi <f(dot)pardi(at)portavita(dot)eu>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Is it ok to run vacuum full verbose command for live database for the tables which has more dead tuples?
Date: 2018-07-18 10:32:45
Message-ID: c9c16dd9-ede1-08fc-cb24-3cf7cf11f7d9@portavita.eu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Raghavendra

answers in line here below:

On 18/07/18 11:13, Raghavendra Rao J S V wrote:
> We have thousands of tables. But out of those tables, around 20 to 40 tables are always busy due to that those tables are bloating.
>
> In order to avoid this we are running a shell script which performs vacuum full on the tables which has more than ten thousand dead tuples. While running this we are stopping all application processors and running vacuum full on the tables which has more dead tuples.
>
> 1. Is it ok to run *vacuum full verbose* command for live database for the tables which has more dead tuples(greater than)?
>
nope

> 1. Does it cause any *adverse *effect?
>
>
exclusively locks the table. Recipe for disaster.

What's wrong with the normal operations of autovacuum?

regards,

fabio pardi

> Please clarify me. Thanks in advance.
>
> --
> Regards,
> Raghavendra Rao J S V
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2018-07-18 13:06:08 Re: A bit confused about "pgsql_tmp" vs "temp tablespace"
Previous Message Hans Schou 2018-07-18 10:25:56 Re: Shared buffers increased but cache hit ratio is still 85%