Re: Long-running and non-finishing VACUUM ANALYZE on large table

From: Ben Primrose <bprimrose(at)tracelink(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Long-running and non-finishing VACUUM ANALYZE on large table
Date: 2015-10-05 12:59:38
Message-ID: 6c446a97aa43e894916e8266c9e3d3ff@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Good to know, thanks for the response.
Ben

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

Ben Primrose <bprimrose(at)tracelink(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Guo, Yun 2015-10-05 17:05:46 Re: pg_upgrade from 9.3 to 9.4 fails
Previous Message Tom Lane 2015-10-02 20:15:49 Re: Long-running and non-finishing VACUUM ANALYZE on large table