| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Lamar Owen" <lamar(dot)owen(at)wgcr(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RPMS for 7.3 beta. |
| Date: | 2002-09-18 02:27:10 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOAEEICEAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I just want people to not get bit in a bad way and decide they
> don't want to
> use PostgreSQL after all. And with the new features of 7.3, lots
> of users
> who might have begun with 7.2 are going to want to upgrade -- but
> if it's too
> painful.... Sorry, it's just a sore spot for me, this whole
> upgrade issue.
> I know Oliver has the same problem, with slightly different presentation.
IS there any solution to Postgres's upgrade problems? I mean, ever? With
the complex catalog design, etc - how is it every possible for us to do a
plug-n-play major version upgrade (assuming datafile format doesn't change
anymore)
How does pg_upgrade work?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-18 02:53:41 | Re: RPMS for 7.3 beta. |
| Previous Message | Lamar Owen | 2002-09-18 02:12:34 | Re: RPMS for 7.3 beta. |