Обсуждение: General migration question
Probably questions best asked on hackers but I figure many are represented here. Will there ever be a release where a dump-restore is not necessary? Perhaps, at least, minor releases (e.g. 9.0 to 9.1) will not require a dump-restore? From 9.0 Release Notes: E.1.2. Migration to Version 9.0 A dump/restore using pg_dump, or use of pg_upgrade, is required for those wishing to migrate data from any previous release. Version 9.0 contains a number of changes that selectively break backwards compatibility in order to support new features and code quality improvements. Also, users who make extensive use of PL/pgSQL, Point-In-Time Recovery (PITR), and Warm Standby should test their solutions because of slight user-visible changes in these areas.
Excerpts from Greg Spiegelberg's message of mar ago 31 09:04:18 -0400 2010: > Probably questions best asked on hackers but I figure many are represented here. > Will there ever be a release where a dump-restore is not necessary? > Perhaps, at least, minor releases (e.g. 9.0 to 9.1) will not require a > dump-restore? 9.0 to 9.1 is not a minor release. 9.0.0 to 9.0.1 is a minor release, and this doesn't require a dump/reload, but it also doesn't have any new features. 9.0 to 9.1 is just as major as 8.4 to 9.0 is. (The rule is: a change in second digit is major release, a change in first digit is marketing pressure) You can upgrade in place using pg_upgrade from 8.4 to 9.0 (thus you don't need dump/reload). In general, it will be possible to migrate from one major version to the next with pg_upgrade starting with the 8.4-to-9.0 jump. -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
On Tue, Aug 31, 2010 at 9:07 AM, Alvaro Herrera <alvherre@commandprompt.com> wrote: > Excerpts from Greg Spiegelberg's message of mar ago 31 09:04:18 -0400 2010: >> Probably questions best asked on hackers but I figure many are represented here. >> Will there ever be a release where a dump-restore is not necessary? >> Perhaps, at least, minor releases (e.g. 9.0 to 9.1) will not require a >> dump-restore? > > 9.0 to 9.1 is not a minor release. 9.0.0 to 9.0.1 is a minor release, > and this doesn't require a dump/reload, but it also doesn't have any new > features. 9.0 to 9.1 is just as major as 8.4 to 9.0 is. (The rule is: > a change in second digit is major release, a change in first digit is > marketing pressure) Okay, wrong terminology. I meant minor release as in Major.Minor.Maintenance. > You can upgrade in place using pg_upgrade from 8.4 to 9.0 (thus you > don't need dump/reload). In general, it will be possible to migrate > from one major version to the next with pg_upgrade starting with the > 8.4-to-9.0 jump. I knew of the pg_upgrade but it's the "in general" part that still makes it a possible bad pill to swallow. All I'm suggesting is lumping those things requiring a dump/restore together for major updates. Greg
On Tue, Aug 31, 2010 at 9:33 AM, Greg Spiegelberg <gspiegelberg@gmail.com> wrote: > On Tue, Aug 31, 2010 at 9:07 AM, Alvaro Herrera > <alvherre@commandprompt.com> wrote: >> Excerpts from Greg Spiegelberg's message of mar ago 31 09:04:18 -0400 2010: >>> Probably questions best asked on hackers but I figure many are represented here. >>> Will there ever be a release where a dump-restore is not necessary? >>> Perhaps, at least, minor releases (e.g. 9.0 to 9.1) will not require a >>> dump-restore? >> >> 9.0 to 9.1 is not a minor release. 9.0.0 to 9.0.1 is a minor release, >> and this doesn't require a dump/reload, but it also doesn't have any new >> features. 9.0 to 9.1 is just as major as 8.4 to 9.0 is. (The rule is: >> a change in second digit is major release, a change in first digit is >> marketing pressure) > > Okay, wrong terminology. I meant minor release as in Major.Minor.Maintenance. But you do understand that in pgsql, it's major.major.minor right? > All I'm suggesting is lumping those things requiring a dump/restore > together for major updates. That's exactly what does happen, if you remember that pgsql is numbered major.major.minor. From 8.3 to 8.4, dump restore, 8.4 to 9.0 dump restore or pg_migrate, and 9.0 to 9.1 will be the same. Now if you meant to save them for 9.x to 10.x? Not gonna happen. That could be years.
On Tue, 2010-08-31 at 09:42 -0600, Scott Marlowe wrote: > > All I'm suggesting is lumping those things requiring a dump/restore > > together for major updates. > > That's exactly what does happen, if you remember that pgsql is > numbered major.major.minor. Perhaps thinking about it like this will help: (major.major).(minor|maintenance) Sincerely, Joshua D. Drake -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579 Consulting, Training, Support, Custom Development, Engineering http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt
On Tue, 2010-08-31 at 09:42 -0600, Scott Marlowe wrote: > > All I'm suggesting is lumping those things requiring a dump/restore > > together for major updates. > > That's exactly what does happen, if you remember that pgsql is > numbered major.major.minor. Perhaps thinking about it like this will help: (major.major).(minor|maintenance) Sincerely, Joshua D. Drake -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579 Consulting, Training, Support, Custom Development, Engineering http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt