From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) |
Cc: | The Hermit Hacker <scrappy(at)hub(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: 7.1 Release Date |
Date: | 2000-08-29 15:43:16 |
Message-ID: | 1935.967563796@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes:
> Will there be a clean upgrade path this time, or
> yet another dump-initdb-restore procedure?
Still TBD, I think --- right now pg_upgrade would still work, but if
Vadim finishes WAL there's going to have to be a dump/reload for that.
Another certain dump/reload in the foreseeable future will come from
adding tablespace support/changing file naming conventions.
> Unclean upgrades are one of major disadvantages of postgresql FTTB,
> IMHO.
You can always stick to Postgres 6.5 :-). There are certain features
that just cannot be added without redoing the on-disk table format.
I don't think we will ever want to promise "no more dump/reload";
if we do, it will mean that Postgres has stopped improving.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alfred Perlstein | 2000-08-29 15:50:41 | Re: Ignore when using COPY FROM |
Previous Message | Adam Lang | 2000-08-29 15:36:13 | SQL scripts - sequences |