| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Ram Pratap Maurya <ram(dot)maurya(at)lavainternational(dot)in> |
| Cc: | "'pgsql-admin(at)lists(dot)postgresql(dot)org'" <pgsql-admin(at)lists(dot)postgresql(dot)org>, Ashish Chugh <ashish(dot)chugh(at)lavainternational(dot)in> |
| Subject: | Re: PostgreSQL Full Vacuum Taking 5 to 6 hrs. |
| Date: | 2022-02-08 07:08:26 |
| Message-ID: | 20220208070826.6q7tgzumlumzlles@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikhil Shetty | 2022-02-08 07:48:39 | Re: Lost replication slots after pg_upgrade. |
| Previous Message | Julien Rouhaud | 2022-02-08 07:04:04 | Re: Lost replication slots after pg_upgrade. |