Re: PG migration policy - Mailing list pgsql-general

From Sim Zacks
Subject Re: PG migration policy
Date
Msg-id 4F24FFDD.10109@compulab.co.il
Whole thread Raw
In response to PG migration policy  (Allan Kamau <kamauallan@gmail.com>)
Responses Re: PG migration policy  (Bill Moran <wmoran@potentialtech.com>)
List pgsql-general
You are moving to a dedicated server for a reason, most probably
performance.
The intro section of the document should discuss the reasons you are
moving and what you hope to accomplish.

Hardware - The discuss the new platform that you are moving to, in terms
of how it will perform better. Important aspects are memory, disk speed,
RAID set up, cpu (not so much).

Server Configuration
Include:
* Kernel compile options
* params such as shmmax
* file system chosen

Postgresql Configuration:
List each option you are going to change and values you are planing on using

Backup strategy
How often backups will be taken, where they go, if there is an offsite
plan, how often restores are tested.

HA strategy
What are you plans if the server dies.

You should also have a test server where you can test changes without
affecting production. It should have the same configuration as the primary.



On 01/29/2012 08:30 AM, Allan Kamau wrote:
> Hi,
> This is definitely off topic, I apologize.
> We are planning to move our PostgreSQL installation from a shared
> server to a dedicated server. I have been given the responsibility of
> writing a migration policy document for this operation. This would be
> my first such document to put together,
> I am looking for pointers, samples and so on on which to build this
> document for our scenario.
>
> Allan.
>


pgsql-general by date:

Previous
From: Allan Kamau
Date:
Subject: PG migration policy
Next
From: Dmitriy Igrishin
Date:
Subject: Re: Index on parent/child hierarchy