Re: Removing pg_migrator limitations

Robert Haas wrote:
> On Sun, Dec 27, 2009 at 2:16 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > On Sun, Dec 27, 2009 at 9:53 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >> Bruce Momjian wrote:
> >>> There are several pg_migrator limitations that appeared late in the 8.4
> >>> development cycle and were impossible to fix at that point. ?I would
> >>> like to fix them for Postgres 8.5:
> >>>
> >>> ? ? ? ? o ?a user-defined composite data type
> >>> ? ? ? ? o ?a user-defined array data type
> >>> ? ? ? ? o ?a user-defined enum data type
> >>
> >> FYI, these pg_migrator restrictions are now gone when migrating to PG
> >> 8.5, even _from_ PG 8.3.
> >
> > Wow, cool. ?That seems like a good step forward.
>
> It appears that the pg_migrator README needs a bit of revision to make
> it more clear which limitations apply to migration between which
> versions. In particular, the current wording suggests that NONE of
> the limitations apply to 8.3 -> 8.5 migrations, which is not the case
> - e.g. we haven't done anything about the need to rebuild certain
> types of indices.

Very true. I have just made a new pg_migrator release with an updated
README file.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +