Re: pg_migrator and an 8.3-compatible tsvector data type

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type
Date: 2009-05-29 01:03:21
Message-ID: 4A1F3459.80601@agliodbs.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce,

> Sure, but that assumes you have parallel I/O channels; I assume right
> now it is I/O limited.

Even a simple cp will be speeded up between 50% and 150% (depending on
your storage) by doing several files in parallel. However, I'm not sure
that's what you should be spending your time on.

--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-05-29 01:06:14 Re: Python 3.0 does not work with PL/Python
Previous Message Alvaro Herrera 2009-05-29 01:00:07 Re: pg_migrator and an 8.3-compatible tsvector data type