Thread: pg_migrator status for 8.4

pg_migrator status for 8.4

From
Bruce Momjian
Date:
I believe pg_migrator has advanced as far as it is going to for 8.4 and
I am expecting to enter beta next week.  Here are the known pg_migrator
limitations:

---------------------------------------------------------------------------

Currently pg_migrator only supports upgrades from 8.3.X to 8.4.X.
pg_migrator will not work if:
       o  a user column is of data type tsquery       o  a user column is of data type 'name' and is not the first
column

pg_migrator will require a table rebuild if:
       o  a user column is of data type tsvector

pg_migrator will require a reindex if:
       o  an index is of type hash or gin       o  an index uses bpchar_pattern_ops

All failure, rebuild, and reindex cases will be reported by pg_migrator
if they affect your installation;  post-migration scripts to rebuild
tables and indexes will be automatically generated.

In general it is unsafe to access tables referenced in rebuild scripts
until the rebuild scripts have run to completion;  doing so could yield
incorrect results or poor performance.  Tables not referenced in rebuild
scripts can be accessed immediately.


--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


Re: pg_migrator status for 8.4

From
Alvaro Herrera
Date:
Bruce Momjian wrote:

> pg_migrator will require a reindex if:
> 
>         o  an index is of type hash or gin
>         o  an index uses bpchar_pattern_ops

What about varchar_pattern_ops and text_pattern_ops?  Are they not
affected?


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


Re: pg_migrator status for 8.4

From
Tom Lane
Date:
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Bruce Momjian wrote:
>> pg_migrator will require a reindex if:
>> o  an index is of type hash or gin
>> o  an index uses bpchar_pattern_ops

> What about varchar_pattern_ops and text_pattern_ops?  Are they not
> affected?

Nope.  See
http://archives.postgresql.org/pgsql-committers/2008-05/msg00346.php
        regards, tom lane