From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Ian Westmacott <ianw@intellivid.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: cost-based vacuum
Date: Mon, 11 Jul 2005 09:28:52 -0400
Message-ID: <7752.1121088532@sss.pgh.pa.us> (raw)
In-Reply-To: <1121081504.3970.53.camel@localhost.localdomain>
References: <1120839902.20657.197.camel@spectre.intellivid.com>
<1121081504.3970.53.camel@localhost.localdomain>
Simon Riggs <simon@2ndquadrant.com> writes:
>> I don't understand why this would be. I don't think there
>> are any lock issues, and I don't see any obvious I/O issues.
> The ANALYZE commands hold read locks on the tables you wish to write to.
Unless there were more commands that Ian didn't show us, he's not taking
any locks that would conflict with ANALYZE. So I don't believe this is
the explanation.
regards, tom lane
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, simon@2ndquadrant.com, ianw@intellivid.com
Subject: Re: cost-based vacuum
In-Reply-To: <7752.1121088532@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