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 20090528233205.GL5156@alvh.no-ip.org
Whole thread Raw
In response to Re: pg_migrator and an 8.3-compatible tsvector data type  (Tom Lane <tgl@sss.pgh.pa.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  (Greg Smith <gsmith@gregsmith.com>)
List pgsql-hackers
Tom Lane wrote:

> People who want decent performance on partial match queries (or maybe
> even *any* TS queries) are going to have to convert to the new format
> anyway, though, so maybe this isn't something worth putting a whole lot
> of work into.  It might be sufficient if the database conversion
> succeeds but leaves the tsvector columns unusable until they're
> converted.

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).

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: User-facing aspects of serializable transactions
Next
From: Bruce Momjian
Date:
Subject: Re: Python 3.0 does not work with PL/Python