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

Re: pg_migrator and an 8.3-compatible tsvector data type

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)enterprisedb(dot)com>, Josh Berkus <josh(at)agliodbs(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:25:46
Message-ID: 4A1F399A.8010609@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers

Alvaro Herrera wrote:
> Bruce Momjian wrote:
>   
>> Alvaro Herrera wrote:
>>     
>
>   
>>> Why not?  Right now it's single-threaded.  Would it be faster if it ran
>>> several copies in parallel?
>>>       
>> Sure, but that assumes you have parallel I/O channels;  I assume right
>> now it is I/O limited.
>>     
>
> But so does parallel pg_restore, no?
>
>   

Well, no, it assumes you're not saturating your I/O bandwidth, which 
turns out to be the case more often than you might expect, even without 
multiple I/O channels.

cheers

andrew

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2009-05-29 01:26:35
Subject: Re: bytea vs. pg_dump
Previous:From: Greg SmithDate: 2009-05-29 01:23:28
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type

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