From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | jd(at)commandprompt(dot)com, Thom Brown <thom(at)linux(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, "w^3" <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Versioning policy and pg_upgrade |
Date: | 2011-01-29 14:53:35 |
Message-ID: | 201101291453.p0TErZd25102@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Robert Haas wrote:
> On Fri, Jan 28, 2011 at 9:50 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >> Major releases usually change the format of system tables. ?These
> >> changes are often complex, so we do not maintain backward
> >> compatibility. ?Our dump and reload tools do maintain backward
> >> compatibility and are the most reliable way to perform a major version
> >> upgrade. ?Some major releases also change the internal format of data
> >> files; however, in recent releases, we have made an attempt to
> >> minimize such changes. ?In cases where the data file formats have not
> >> changed, pg_upgrade can also be used for major upgrade version
> >> upgrades; this is typically much faster than a dump and reload.
> >
> > That seems quite detailed for the web site. ?If we want that I think we
> > should add those details to the pg_upgrade manual page. ?Some of that is
> > already there.
>
> It's not that much more than you wrote, and it has the redeeming value
> of being accurate...
I added five words.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-01-29 15:27:13 | Re: Versioning policy and pg_upgrade |
Previous Message | Thom Brown | 2011-01-29 13:34:32 | Re: Versioning policy and pg_upgrade |