| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
| Cc: | Alvaro Herrera <alvherre(at)atentus(dot)com>, Justin Clift <justin(at)postgresql(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Upgrade process (was Re: 7.2.3?) |
| Date: | 2002-09-28 21:22:02 |
| Message-ID: | 4938.1033248122@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
> This is of course a two-edged sword.
> 1.) Keeping pg_upgrade working, which depends upon pg_dump working;
... which we have to have anyway, of course ...
> 2.) Maintaining security fixes for 7.2 for a good period of time to come,
> since migration from 7.2 to >7.2 isn't easy.
True, but I think we'll have to deal with that anyway. Even if the
physical database upgrade were trivial, people are going to find
application compatibility problems due to schemas and other 7.3 changes.
So we're going to have to expend at least some work on fixing critical
7.2.* problems. (I just want to keep a tight rein on how much.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Clift | 2002-09-28 21:30:35 | Re: 7.2.3? |
| Previous Message | Lamar Owen | 2002-09-28 21:05:58 | Re: Upgrade process (was Re: 7.2.3?) |