Hi,
> > Is there any other option to increase the speed of vacuum?
>
> For autovacuum, decrease "autovacuum_vacuum_cost_delay".
He mentioned in the original message that his problems was with a
global VACUUM after upgrading, so cost_delay should be zero by
default.
Regards,
--
Martín Marqués
I
On Tue, 2021-02-02 at 13:44 +0530, Atul Kumar wrote:
> Is there any other option to increase the speed of vacuum?
For autovacuum, decrease "autovacuum_vacuum_cost_delay".
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
Ok Martin, I got ur ur point of max limit of maintenance_work_mem is 1 GB
but there is nothing mentioned about the same in postgresql.conf as remarks
for this specific parameter.
Is there any other option to increase the speed of vacuum?
Regards
Atul
On Tuesday, February 2, 2021, Martín Mar
Hi Atul,
> We have DB of 400GBs, Server RAM is 160GBs. CPU consumption is 1-3% only.
>
> We have configured maintenance_work_mem to 10GBs and restarted the
> postgres service.
Just wanted to mention that maintenance_work_mem has a hardcoded upper
limit threshold of 1GB, so any size bigger than
Assuming that the system is online and in use, you may want to consider
doing analyze first to ensure stats are proper, and then vacuum all
less-used tables that should be quick then larger/more active tables with
the verbose option to see details of why it might be taking time. If you
are seeing m
Hi,
We have DB of 400GBs, Server RAM is 160GBs. CPU consumption is 1-3% only.
We have configured maintenance_work_mem to 10GBs and restarted the
postgres service.
We have done upgrade from postgres 9.5 to 9.6, then when we run vacuum
analyze on database, it is taking more than 5 hours and stil
