Re: Long-running and non-finishing VACUUM ANALYZE on large table - Mailing list pgsql-admin

From Ben Primrose
Subject Re: Long-running and non-finishing VACUUM ANALYZE on large table
Date
Msg-id 6c446a97aa43e894916e8266c9e3d3ff@mail.gmail.com
Whole thread Raw
In response to Re: Long-running and non-finishing VACUUM ANALYZE on large table  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Good to know, thanks for the response.
Ben

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Friday, October 02, 2015 4:16 PM
To: Ben Primrose
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Long-running and non-finishing VACUUM ANALYZE on
large table

Ben Primrose <bprimrose@tracelink.com> writes:
> Tom, how'd you determine the maintenance_work_mem?

From the numbers of tuples shown as being removed in each index pass.
The work-mem usage is 6 bytes per TID, and it'll stop and do an index pass
once we get close to full.

            regards, tom lane


pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Long-running and non-finishing VACUUM ANALYZE on large table
Next
From: "Guo, Yun"
Date:
Subject: Re: pg_upgrade from 9.3 to 9.4 fails