Re: autovacuum: multiple workers - Mailing list pgsql-patches

From Simon Riggs
Subject Re: autovacuum: multiple workers
Date
Msg-id 1175035296.4386.246.camel@silverbirch.site
Whole thread Raw
In response to autovacuum: multiple workers  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: autovacuum: multiple workers  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-patches
On Tue, 2007-03-27 at 17:41 -0400, Alvaro Herrera wrote:

> The main change is to have an array of Worker structs in shared memory;
> each worker checks the current table of all other Workers, and skips a
> table that's being vacuumed by any of them.  It also rechecks the table
> before vacuuming, which removes the problem of redundant vacuuming.

Slightly OT: Personally, I'd like it if we added an array for all
special backends, with configurable behaviour. That way it would be
easier to have multiple copies of other backends of any flavour using
the same code, as well as adding others without cutting and pasting each
time. That part of the postmaster code has oozed sideways in the past
few years and seems in need of some love. (A former sinner repents).

--
  Simon Riggs
  EnterpriseDB   http://www.enterprisedb.com



pgsql-patches by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: Patch for circular buffer in tuplestore to optimizemerge joins (v1)
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] add CLUSTER table ORDER BY index