Re: backup-strategies for large databases - Mailing list pgsql-general

From Scott Marlowe
Subject Re: backup-strategies for large databases
Date
Msg-id CAOR=d=1_VSAZy64Ho7Jrk2LGN3DdAqOkrM0PgHT_B6tOfohumw@mail.gmail.com
Whole thread Raw
In response to backup-strategies for large databases  (MirrorX <mirrorx@gmail.com>)
Responses Re: backup-strategies for large databases  (MirrorX <mirrorx@gmail.com>)
Re: backup-strategies for large databases  (MirrorX <mirrorx@gmail.com>)
List pgsql-general
One possible answer to your issues is data partitioning.  By
partitioning your data by date or primary key or some other field, you
can backup individual partitions for incremental backups. I run a
stats database that partitions by day daily and we can just backup
yesterday's partition each night.  Each partition is in the 10 to 20
meg size range.

pgsql-general by date:

Previous
From: Greg Williamson
Date:
Subject: Re: Using Postgresql as application server
Next
From: Rafal Pietrak
Date:
Subject: INSERT-colision/MERGE in postgresql