Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Installation Steps to migrate to Postgres 8.3.1
- From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
- To: "Knight, Doug" <dknight(at)wsi(dot)com>
- Cc: "Gauri Kanekar" <meetgaurikanekar(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
- Subject: Re: Installation Steps to migrate to Postgres 8.3.1
- Date: Tue, 13 May 2008 08:37:59 -0600
- Message-id: <dcc563d10805130737h5dae8dfax51fd1799af9098d7(at)mail(dot)gmail(dot)com>
On Tue, May 13, 2008 at 6:00 AM, Knight, Doug <dknight(at)wsi(dot)com> wrote: > Hi, > Along these lines, the usual upgrade path is a pg_dump/pg_restore set. > However, what if your database is large (> 50GB), and you have to > minimize your downtime (say less than an hour or two). Any suggestions > on how to handle that kind of situation? It sure would be nice to have > some kind of tool to update in-place a database, though I know that's > not a likely path. look up Slony
- References:
- Installation Steps to migrate to Postgres 8.3.1
- From: Gauri Kanekar
- Re: Installation Steps to migrate to Postgres 8.3.1
- From: Scott Marlowe
- Re: Installation Steps to migrate to Postgres 8.3.1
- From: Knight, Doug
- Installation Steps to migrate to Postgres 8.3.1
- Prev by Date: Re: Installation Steps to migrate to Postgres 8.3.1
- Next by Date: Re: RAID controllers for Postgresql on large setups
- Previous by thread: Re: Installation Steps to migrate to Postgres 8.3.1
- Next by thread: Problem with 11 M records table
- Indexes: