From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Subject: | Re: Removing pg_migrator limitations |
Date: | 2009-12-20 19:39:01 |
Message-ID: | 3874.1261337941@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I agree that pulling pg_migrator into contrib seems pretty sensible.
> What I want to make sure we're on the same page about is which
> versions the 8.5 pg_migrator will allow you to upgrade from and to. I
> think we should at least support 8.3 -> 8.5 and 8.4 -> 8.5. If you're
> saying we don't need to support 8.3 -> 8.4 any more once 8.5 comes
> out, I'm probably OK with that, but perhaps we should try to get a few
> more opinions before setting that policy in stone.
If we can do that reasonably (which might well be the case), I'd be for
it. What I'm objecting to is what I take to be Bruce's plan of
supporting 8.3 -> 8.4 and 8.4 -> 8.5 with the same pg_migrator sources.
The stuff we're talking about doing in this thread is going to cause
those two cases to diverge rather drastically. 8.3 -> 8.5 and 8.4 ->
8.5 may be close enough together to be reasonable to support in one
set of source code.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | James William Pye | 2009-12-20 19:53:43 | Re: alpha3 bundled -- please verify |
Previous Message | Simon Riggs | 2009-12-20 19:30:44 | Re: alpha3 release schedule? |