Skip site navigation (1) Skip section navigation (2)

Re: Backing up large databases

From: Jim Nasby <jnasby(at)pervasive(dot)com>
To: <andy(dot)shellam(at)mailnetwork(dot)co(dot)uk>
Cc: "'Steve Burrows'" <steve(at)jla(dot)com>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Backing up large databases
Date: 2006-04-29 01:30:00
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On Apr 28, 2006, at 10:34 AM, Andy Shellam wrote:
> My future plan for when my database grows larger, is with the use  
> of WAL logging – have a base backup taken on a Sunday morning (our  
> quietest time), ship this to the hot-standby once a week, and start  
> it off in a recovery mode (using my rolling-WAL script I’m testing  
> now.)  Then throughout the week, send the WAL logs from the live  
> box as they become available down to the standby, which then get  
> processed on arrival – these files are 16MB in size (I believe this  
> can be changed).
Theoretically the size of WAL files can be changed, but in practice  
no one ever does this. In other words, it's probably not a great idea.
> This is coming from an 8.1 server, I believe it’d be okay for 7.4  
> but don’t quote me on it.
PITR was introduced in 8.0. There's a number of other reasons to  
upgrade as well. In the meantime, Slony might be a viable alternative.
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software    work: 512-231-6117
vcard:       cell: 512-569-9461

In response to

pgsql-admin by date

Next:From: Jim NasbyDate: 2006-04-29 01:34:15
Subject: Re: WAL recovery question - 0000001.history
Previous:From: alex.cotarlanDate: 2006-04-28 22:46:30
Subject: Re: Backing up large databases

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group