Skip site navigation (1) Skip section navigation (2)

Re: autovacuum: multiple workers

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Cc: "Patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: autovacuum: multiple workers
Date: 2007-03-27 22:41:36
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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             

In response to


pgsql-patches by date

Next:From: Tom LaneDate: 2007-03-28 01:01:30
Subject: Re: [PATCH] add CLUSTER table ORDER BY index
Previous:From: Simon RiggsDate: 2007-03-27 22:33:21
Subject: Re: Patch for circular buffer in tuplestore to optimizemerge joins (v1)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group