Subject: Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs.
To: pgsql-admin@lists.postgresql.org
References: 
 <KL1PR0601MB443336C9B802CED1A9B9B1E1F02D9@KL1PR0601MB4433.apcprd06.prod.outlook.com>
 <20220208065324.6lrlrqxvau33k5gk@jrouhaud>
 <KL1PR0601MB44339FD28B5E47B77799B42AF02D9@KL1PR0601MB4433.apcprd06.prod.outlook.com>
 <20220208070826.6q7tgzumlumzlles@jrouhaud>
 <KL1PR0601MB443373ADB38E18DE4494C534F02D9@KL1PR0601MB4433.apcprd06.prod.outlook.com>
From: Ron <ronljohnsonjr@gmail.com>
Message-ID: <c5b82cb9-bdfd-d782-a438-94967a816562@gmail.com>
Date: Tue, 8 Feb 2022 08:11:44 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: 
 <KL1PR0601MB443373ADB38E18DE4494C534F02D9@KL1PR0601MB4433.apcprd06.prod.outlook.com>
Content-Type: multipart/alternative;
 boundary="------------31C6D8E3360B2EE5F8F30C94"
Content-Language: en-US
Archived-At: 
 <https://www.postgresql.org/message-id/c5b82cb9-bdfd-d782-a438-94967a816562%40gmail.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------31C6D8E3360B2EE5F8F30C94
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Maybe your database is really big.
Maybe your storage subsystem is really slow.
Maybe you're only running one thread.
Maybe it's being blocked by other users.

We don't know because you've barely told us anything.

Not to mention: VACUUM FULL is *only* useful after you've updated or deleted 
a major portion of a table all at once.

On 2/8/22 5:22 AM, Ram Pratap Maurya wrote:
> HI Julien,
>
> In my current database index size is very large compare than table (if table size is 30 GB and index size is 90GB) , that why We running full vacuum monthly basis to increase the system performance and data reclaim .
> Auto Vacuum is also configuration in system.
> As per your suggesion if we increase " maintenance_work_mem " paramater size to 1GB this will be help to improve full vacuum performance?.
>
> System configuration as below:
>
> CPU - 42
> RAM -70GB
>
>
>
> Regards,
> Ram Pratap.
>
> -----Original Message-----
> From: Julien Rouhaud [mailto:rjuju123@gmail.com]
> Sent: 08 February 2022 12:38
> To: Ram Pratap Maurya
> Cc: 'pgsql-admin@lists.postgresql.org'; Ashish Chugh
> Subject: Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs.
>
> Hi,
>
> Please don't top post on those forums
> (https://wiki.postgresql.org/wiki/Mailing_Lists#Email_etiquette_mechanics)
>
> On Tue, Feb 08, 2022 at 06:59:07AM +0000, Ram Pratap Maurya wrote:
>> we are running VACUUM FULL on all table and its take 5 to 6 Hrs.
> The only thing that can be done to make it faster is to use a 1GB maintenance_work_mem.
>
> But why do you need to do frequent database wide VACUUM FULL in the first place?  Do you really have massive bloat on every single table in the database?
>
> Do you have adequate autovacuum configuration, or additional VACUUM jobs if that's not enough?
>
>

-- 
Angular momentum makes the world go 'round.

--------------31C6D8E3360B2EE5F8F30C94
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Maybe your database is really big.<br>
    Maybe your storage subsystem is really slow.<br>
    Maybe you're only running one thread.<br>
    Maybe it's being blocked by other users.<br>
    <br>
    We don't know because you've barely told us anything.<br>
    <br>
    Not to mention: VACUUM FULL is <b>only</b> useful after you've
    updated or deleted a major portion of a table all at once.<br>
    <br>
    <div class="moz-cite-prefix">On 2/8/22 5:22 AM, Ram Pratap Maurya
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:KL1PR0601MB443373ADB38E18DE4494C534F02D9@KL1PR0601MB4433.apcprd06.prod.outlook.com">
      <pre class="moz-quote-pre" wrap="">HI Julien,

In my current database index size is very large compare than table (if table size is 30 GB and index size is 90GB) , that why We running full vacuum monthly basis to increase the system performance and data reclaim .
Auto Vacuum is also configuration in system.
As per your suggesion if we increase " maintenance_work_mem " paramater size to 1GB this will be help to improve full vacuum performance?.

System configuration as below:

CPU - 42 
RAM -70GB


Regards,
Ram Pratap.

-----Original Message-----
From: Julien Rouhaud [<a class="moz-txt-link-freetext" href="mailto:rjuju123@gmail.com">mailto:rjuju123@gmail.com</a>] 
Sent: 08 February 2022 12:38
To: Ram Pratap Maurya
Cc: '<a class="moz-txt-link-abbreviated" href="mailto:pgsql-admin@lists.postgresql.org">pgsql-admin@lists.postgresql.org</a>'; Ashish Chugh
Subject: Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs.

Hi,

Please don't top post on those forums
(<a class="moz-txt-link-freetext" href="https://wiki.postgresql.org/wiki/Mailing_Lists#Email_etiquette_mechanics">https://wiki.postgresql.org/wiki/Mailing_Lists#Email_etiquette_mechanics</a>)

On Tue, Feb 08, 2022 at 06:59:07AM +0000, Ram Pratap Maurya wrote:
</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">
we are running VACUUM FULL on all table and its take 5 to 6 Hrs.
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
The only thing that can be done to make it faster is to use a 1GB maintenance_work_mem.

But why do you need to do frequent database wide VACUUM FULL in the first place?  Do you really have massive bloat on every single table in the database?

Do you have adequate autovacuum configuration, or additional VACUUM jobs if that's not enough?


</pre>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      Angular momentum makes the world go 'round.</div>
  </body>
</html>

--------------31C6D8E3360B2EE5F8F30C94--