pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Alvaro Herrera <alvherre@commandprompt.com>
To: Uwe Bartels <uwe.bartels@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: blocking automatic vacuum
Date: Thu, 01 Jul 2010 11:33:57 -0400
Message-ID: <1277998392-sup-5801@alvh.no-ip.org> (raw)
In-Reply-To: <AANLkTimb66dmMOxl-hGDPeQfnCTlFYksPJSy2jbN3w3R@mail.gmail.com>
References: <AANLkTikICmG_zdZRULEsoBSvxzRuPxwPgomRUsAVWgWl@mail.gmail.com>
	<1494.1277218083@sss.pgh.pa.us>
	<AANLkTimb66dmMOxl-hGDPeQfnCTlFYksPJSy2jbN3w3R@mail.gmail.com>

Excerpts from Uwe Bartels's message of jue jul 01 04:42:42 -0400 2010:
> Hi Tom,
> 
> till now i found more blocking vacuum processes in other databases as well.
> we migrated postgres from 8.3 to 8.4 in april.

Please examine pg_locks to see what's blocking autovacuum.  The key is
WHERE granted=f.

view thread (8+ messages)

Message-ID: <1277998392-sup-5801@alvh.no-ip.org>
Permalink:  ../1277998392-sup-5801@alvh.no-ip.org/
Also on:    postgresql.org/message-id/1277998392-sup-5801@alvh.no-ip.org

copy link · copy postgr.es

reply

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: alvherre@commandprompt.com, uwe.bartels@gmail.com, tgl@sss.pgh.pa.us
  Subject: Re: blocking automatic vacuum
  In-Reply-To: <1277998392-sup-5801@alvh.no-ip.org>

* 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