From: Alvaro Herrera <alvherre@commandprompt.com>
To: Dimitri <dimitrik.fr@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Parallel Vacuum
Date: Thu, 22 Mar 2007 11:12:50 -0400
Message-ID: <20070322151243.GH4102@alvh.no-ip.org> (raw)
In-Reply-To: <200703221605.38460.dimitrik.fr@gmail.com>
References: <200703221435.54408.dimitrik.fr@gmail.com>
<20070322135205.GD4102@alvh.no-ip.org>
<200703221605.38460.dimitrik.fr@gmail.com>
Dimitri escribió:
> On Thursday 22 March 2007 14:52, Alvaro Herrera wrote:
> > Dimitri escribió:
> > > Folks,
> > >
> > > is there any constrains/problems/etc. to run several vacuum processes in
> > > parallel while each one is 'vaccuming' one different table?
> >
> > No, no problem. Keep in mind that if one of them takes a very long
> > time, the others will not be able to remove dead tuples that were
> > killed while the long vacuum was running -- unless you are in 8.2.
>
> Yes, I'm using the last 8.2.3 version. So, will they *really* processing in
> parallel, or will block each other step by step?
They won't block.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: alvherre@commandprompt.com, dimitrik.fr@gmail.com
Subject: Re: Parallel Vacuum
In-Reply-To: <20070322151243.GH4102@alvh.no-ip.org>
References: <200703221435.54408.dimitrik.fr@gmail.com> <20070322135205.GD4102@alvh.no-ip.org> <200703221605.38460.dimitrik.fr@gmail.com> <20070322151243.GH4102@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