pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgreSQL Full Vacuum Taking 5 to 6 hrs.
8+ messages / 3 participants
[nested] [flat]
* PostgreSQL Full Vacuum Taking 5 to 6 hrs.
@ 2022-02-08 06:25 Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 06:53 ` Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Julien Rouhaud <rjuju123@gmail.com>
2022-02-08 11:33 ` RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
0 siblings, 2 replies; 8+ messages in thread
From: Ram Pratap Maurya @ 2022-02-08 06:25 UTC (permalink / raw)
To: 'pgsql-admin@lists.postgresql.org' <pgsql-admin@lists.postgresql.org>; +Cc: Ashish Chugh <ashish.chugh@lavainternational.in>
Hi Team,
We are using Postgres -11 version and when we running Full vacuum it will take 5 to 6 Hrs to complete full vacuum.
Please suggest how to reduce the full vacuum time.
OS Version : RHEL6
DB size -450 GB
Postgresql Version -11
Regards,
Ram Pratap.
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs.
2022-02-08 06:25 PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
@ 2022-02-08 06:53 ` Julien Rouhaud <rjuju123@gmail.com>
2022-02-08 06:59 ` RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
1 sibling, 1 reply; 8+ messages in thread
From: Julien Rouhaud @ 2022-02-08 06:53 UTC (permalink / raw)
To: Ram Pratap Maurya <ram.maurya@lavainternational.in>; +Cc: 'pgsql-admin@lists.postgresql.org' <pgsql-admin@lists.postgresql.org>; Ashish Chugh <ashish.chugh@lavainternational.in>
Hi,
On Tue, Feb 08, 2022 at 06:25:01AM +0000, Ram Pratap Maurya wrote:
>
> We are using Postgres -11 version and when we running Full vacuum it will
> take 5 to 6 Hrs to complete full vacuum.
What do you mean by "full vacuum" exactly? Is it a plain VACUUM FULL? If yes,
on all tables or only some specific ones?
^ permalink raw reply [nested|flat] 8+ messages in thread
* RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs.
2022-02-08 06:25 PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 06:53 ` Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Julien Rouhaud <rjuju123@gmail.com>
@ 2022-02-08 06:59 ` Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 07:08 ` Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Julien Rouhaud <rjuju123@gmail.com>
0 siblings, 1 reply; 8+ messages in thread
From: Ram Pratap Maurya @ 2022-02-08 06:59 UTC (permalink / raw)
To: Julien Rouhaud <rjuju123@gmail.com>; +Cc: 'pgsql-admin@lists.postgresql.org' <pgsql-admin@lists.postgresql.org>; Ashish Chugh <ashish.chugh@lavainternational.in>
Hi Julien,
we are running VACUUM FULL on all table and its take 5 to 6 Hrs.
Regards,
Ram Pratap.
-----Original Message-----
From: Julien Rouhaud [mailto:rjuju123@gmail.com]
Sent: 08 February 2022 12:23
To: Ram Pratap Maurya
Cc: 'pgsql-admin@lists.postgresql.org'; Ashish Chugh
Subject: Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs.
Hi,
On Tue, Feb 08, 2022 at 06:25:01AM +0000, Ram Pratap Maurya wrote:
>
> We are using Postgres -11 version and when we running Full vacuum it
> will take 5 to 6 Hrs to complete full vacuum.
What do you mean by "full vacuum" exactly? Is it a plain VACUUM FULL? If yes, on all tables or only some specific ones?
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs.
2022-02-08 06:25 PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 06:53 ` Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Julien Rouhaud <rjuju123@gmail.com>
2022-02-08 06:59 ` RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
@ 2022-02-08 07:08 ` Julien Rouhaud <rjuju123@gmail.com>
2022-02-08 11:22 ` RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
0 siblings, 1 reply; 8+ messages in thread
From: Julien Rouhaud @ 2022-02-08 07:08 UTC (permalink / raw)
To: Ram Pratap Maurya <ram.maurya@lavainternational.in>; +Cc: 'pgsql-admin@lists.postgresql.org' <pgsql-admin@lists.postgresql.org>; Ashish Chugh <ashish.chugh@lavainternational.in>
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?
^ permalink raw reply [nested|flat] 8+ messages in thread
* RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs.
2022-02-08 06:25 PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 06:53 ` Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Julien Rouhaud <rjuju123@gmail.com>
2022-02-08 06:59 ` RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 07:08 ` Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Julien Rouhaud <rjuju123@gmail.com>
@ 2022-02-08 11:22 ` Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 11:25 ` RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 14:11 ` Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ron <ronljohnsonjr@gmail.com>
0 siblings, 2 replies; 8+ messages in thread
From: Ram Pratap Maurya @ 2022-02-08 11:22 UTC (permalink / raw)
To: Julien Rouhaud <rjuju123@gmail.com>; +Cc: 'pgsql-admin@lists.postgresql.org' <pgsql-admin@lists.postgresql.org>; Ashish Chugh <ashish.chugh@lavainternational.in>
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?
^ permalink raw reply [nested|flat] 8+ messages in thread
* RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs.
2022-02-08 06:25 PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 06:53 ` Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Julien Rouhaud <rjuju123@gmail.com>
2022-02-08 06:59 ` RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 07:08 ` Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Julien Rouhaud <rjuju123@gmail.com>
2022-02-08 11:22 ` RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
@ 2022-02-08 11:25 ` Ram Pratap Maurya <ram.maurya@lavainternational.in>
1 sibling, 0 replies; 8+ messages in thread
From: Ram Pratap Maurya @ 2022-02-08 11:25 UTC (permalink / raw)
To: Julien Rouhaud <rjuju123@gmail.com>; +Cc: 'pgsql-admin@lists.postgresql.org' <pgsql-admin@lists.postgresql.org>; Ashish Chugh <ashish.chugh@lavainternational.in>
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.
" maintenance_work_mem " paramater size to 2GB configure in system.
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?
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs.
2022-02-08 06:25 PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 06:53 ` Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Julien Rouhaud <rjuju123@gmail.com>
2022-02-08 06:59 ` RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 07:08 ` Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Julien Rouhaud <rjuju123@gmail.com>
2022-02-08 11:22 ` RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
@ 2022-02-08 14:11 ` Ron <ronljohnsonjr@gmail.com>
1 sibling, 0 replies; 8+ messages in thread
From: Ron @ 2022-02-08 14:11 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
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.
^ permalink raw reply [nested|flat] 8+ messages in thread
* RE: PostgreSQL Full Vacuum Taking 5 to 6 hrs.
2022-02-08 06:25 PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
@ 2022-02-08 11:33 ` Ram Pratap Maurya <ram.maurya@lavainternational.in>
1 sibling, 0 replies; 8+ messages in thread
From: Ram Pratap Maurya @ 2022-02-08 11:33 UTC (permalink / raw)
To: 'pgsql-admin@lists.postgresql.org' <pgsql-admin@lists.postgresql.org>; +Cc: Ashish Chugh <ashish.chugh@lavainternational.in>
Hi Team,
We are using Postgres -11 version and current PG DB size is 450 GB .
Archive log enable in Database and we are running Full PG_Base backup and it will take 8 to 8:30 Hrs to complete the backup ,
Please suggest how to reduce the full DB backup time.
OS Version : RHEL6
DB size -450 GB
Postgresql Version -11
Regards,
Ram Pratap.
^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2022-02-08 14:11 UTC | newest]
Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-02-08 06:25 PostgreSQL Full Vacuum Taking 5 to 6 hrs. Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 06:53 ` Julien Rouhaud <rjuju123@gmail.com>
2022-02-08 06:59 ` Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 07:08 ` Julien Rouhaud <rjuju123@gmail.com>
2022-02-08 11:22 ` Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 11:25 ` Ram Pratap Maurya <ram.maurya@lavainternational.in>
2022-02-08 14:11 ` Ron <ronljohnsonjr@gmail.com>
2022-02-08 11:33 ` Ram Pratap Maurya <ram.maurya@lavainternational.in>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox