From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ben Primrose <bprimrose@tracelink.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Long-running and non-finishing VACUUM ANALYZE on large table
Date: Fri, 02 Oct 2015 16:15:49 -0400
Message-ID: <4139.1443816949@sss.pgh.pa.us> (raw)
In-Reply-To: <26437172ca27bd83e46c2a8db18401bb@mail.gmail.com>
References: <560EB550.5050501@j.mk-contact.de>
<23918.1443806166@sss.pgh.pa.us>
<26437172ca27bd83e46c2a8db18401bb@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Ben Primrose <bprimrose@tracelink.com> writes:
> Tom, how'd you determine the maintenance_work_mem?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, bprimrose@tracelink.com
Subject: Re: Long-running and non-finishing VACUUM ANALYZE on large table
In-Reply-To: <4139.1443816949@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox