| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_migrator to /contrib in a later 9.0 beta |
| Date: | 2010-05-02 19:06:21 |
| Message-ID: | 201005021906.o42J6La21133@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
> Well, that is going to make the documentation more complicated than it
> already is. Why mention a process in 9.0 that no one needs to use? I
> am not writing the docs for some hypothetical release, but for 9.0.
> When we have some restriction, we can document that.
>
> My guess is that 9.2 will be able to upgrade from 8.3, 8.4, 9.0, and
> 9.1, but that going to 9.5 will require you to go to 9.2 first, run some
> script, then upgrade to 9.5; again all hypothetical. I think we can
> require people using pg_migrator to read matching documentation for that
> major version of pg_migrator, and pg_migrator will enforce any
> restrictions we come up with in the future. For example, I assume there
> will be some major version of Postgres where pg_migrator will not work
> at all.
I do think we are going to have to mention new pg_migrator restrictions
in the major release notes for future versions.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2010-05-02 19:30:37 | Re: pg_migrator to /contrib in a later 9.0 beta |
| Previous Message | Bruce Momjian | 2010-05-02 19:01:34 | Re: Further Hot Standby documentation required |