Re: Postgres wal shipping from 8.33 to 8.42.
| От | Scott Marlowe |
|---|---|
| Тема | Re: Postgres wal shipping from 8.33 to 8.42. |
| Дата | |
| Msg-id | dcc563d11002040812k67fb6246o7d9cdc76090e8df8@mail.gmail.com обсуждение |
| Ответ на | Re: Postgres wal shipping from 8.33 to 8.42. (Thom Brown <thombrown@gmail.com>) |
| Список | pgsql-general |
On Thu, Feb 4, 2010 at 8:58 AM, Thom Brown <thombrown@gmail.com> wrote: > On 4 February 2010 15:54, Scott Marlowe <scott.marlowe@gmail.com> wrote: >> On Thu, Feb 4, 2010 at 7:54 AM, Chris Barnes >> <compuguruchrisbarnes@hotmail.com> wrote: >>> We are trying to minimize our downtime in production to upgrade from 8.33 to >>> 8.42. >>> >>> What we would like to be able to do is this: >>> Upgrade the slave we are currently shipping to, to version 8.4.2. Continue >>> to pitr to this server. And switch over and then upgrade the master. >>> >>> My question is, will pitr wal logs ship and be processed from a machine >>> running 8.33 to 8.42. >> >> Nope. But you can use slony to upgrade. >> > > Or pg_migrator? http://pgfoundry.org/projects/pg-migrator For minimal downtime, slony would win, but for reducing effort, pg_migrator wins.
В списке pgsql-general по дате отправления: