From: Ben Primrose <bprimrose@tracelink.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Long-running and non-finishing VACUUM ANALYZE on large table
Date: Mon, 5 Oct 2015 08:59:38 -0400
Message-ID: <6c446a97aa43e894916e8266c9e3d3ff@mail.gmail.com> (raw)
In-Reply-To: <4139.1443816949@sss.pgh.pa.us>
References: <560EB550.5050501@j.mk-contact.de>
<23918.1443806166@sss.pgh.pa.us>
<26437172ca27bd83e46c2a8db18401bb@mail.gmail.com>
<4139.1443816949@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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?
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: bprimrose@tracelink.com, tgl@sss.pgh.pa.us
Subject: Re: Long-running and non-finishing VACUUM ANALYZE on large table
In-Reply-To: <6c446a97aa43e894916e8266c9e3d3ff@mail.gmail.com>
* 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