Re: 9.3 feature proposal: vacuumdb -j # - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: 9.3 feature proposal: vacuumdb -j #
Date
Msg-id B6107D76-1824-400C-ADC9-F01AA1D19E7A@nasby.net
Whole thread Raw
In response to Re: 9.3 feature proposal: vacuumdb -j #  (Christopher Browne <cbbrowne@gmail.com>)
Responses Re: 9.3 feature proposal: vacuumdb -j #  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Jan 13, 2012, at 4:15 PM, Christopher Browne wrote:
> Have two logical tasks:
> a) A process that manages the list, and
> b) Child processes doing vacuums.
>
> Each time a child completes a table, it asks the parent for another one.

There is also a middle ground, because having the the scheduling process sounds like a lot more work than what Josh was
proposing.

CREATE TEMP SEQUENCE s;
SELECT relname, s mod <number of backends> AS backend_number FROM ( SELECT relname          FROM pg_class
ORDERBY relpages 
);

Of course, having an actual scheduling process is most likely the most efficient.
--
Jim C. Nasby, Database Architect                   jim@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net




pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: how to create a non-inherited CHECK constraint in CREATE TABLE
Next
From: Jim Nasby
Date:
Subject: Re: Group commit, revised