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

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

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

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ben Primrose 2015-10-05 12:59:38 Re: Long-running and non-finishing VACUUM ANALYZE on large table
Previous Message Tom Lane 2015-10-02 17:16:06 Re: Long-running and non-finishing VACUUM ANALYZE on large table