> So, one idea would be, instead of a cast, have pg_migrator rebuild the
> tsvector columns with ALTER TABLE, so then the 8.4 index code could be
> used. But then we might as well just tell the users to migrate the
> tsvector tables themselves, which is how pg_migrator behaves now.
It would be nice to have pg_migrator handle this, especially if we could
do it in parallel. Then we just have to warn users that migrating a
database with tsvector columns takes significantly longer. That is,
1) do rest of catalog swap and link/copy of objects.
2) mark all tsvector columns as 83_tsvector and add new tsvector type
(these columns will be unusable for queries)
3) bring up database
4) search for all 83_tsvector columns
5) do ALTER TABLE on each of these columns, in parallel, up to a
configuration setting (default 3).
However, I can also understand not having time to implement the above
before 8.4 release.
PostgreSQL Experts Inc.
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2009-05-29 18:39:23|
|Subject: Re: explain analyze rows=%.0f|
|Previous:||From: Tom Lane||Date: 2009-05-29 18:35:59|
|Subject: Re: information_schema.columns changes needed for OLEDB |