Re: pg_migrator and an 8.3-compatible tsvector data type - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pg_migrator and an 8.3-compatible tsvector data type
Date
Msg-id 20090529002601.GM5156@alvh.no-ip.org
Whole thread Raw
In response to Re: pg_migrator and an 8.3-compatible tsvector data type  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_migrator and an 8.3-compatible tsvector data type  (Bruce Momjian <bruce@momjian.us>)
Re: pg_migrator and an 8.3-compatible tsvector data type  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
List pgsql-hackers
Bruce Momjian wrote:
> Alvaro Herrera wrote:

> > There are so many caveats on pg_migrator (and things that need to be
> > done after the migration is complete) that one starts to wonder if
> > people is not better off just using parallel pg_restore.  From Stefan's
> > reported timings I'm not sure that pg_migrator is that much of a benefit
> > in the first place ... unless copy mode can be made much faster.  (On
> > link mode it is so much faster that it's worth it, but then you don't
> > have an escape hatch).
> 
> That is accurate.  I doubt copy mode speed can be improved.

Why not?  Right now it's single-threaded.  Would it be faster if it ran
several copies in parallel?

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: User-facing aspects of serializable transactions
Next
From: Robert Haas
Date:
Subject: Re: PostgreSQL Developer meeting minutes up