From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | MirrorX <mirrorx(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: backup-strategies for large databases |
Date: | 2011-08-15 23:12:30 |
Message-ID: | CAOR=d=33Bdx6b0MtTODJUjERYTvXU=CSzJv-WP6OPS+05wD5eQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Aug 15, 2011 at 5:06 PM, MirrorX <mirrorx(at)gmail(dot)com> wrote:
> i looked into data partitioning and it is definitely something we will use
> soon. but, as far as the backups are concerned, how can i take a backup
> incrementally? if i get it correctly, the idea is to partition a big table
> (using a date field for example) and then take each night for example a dump
> of the 'daily' partition. so that the dump of this specific table will be
> relatively small to the size of the initial table. is that right?
>
> so, we are talking about logical backups without PITR. i am not saying that
> it's a bad idea, i just want to make sure that i got it right.
Exactly. Sometimes PITR is the right answer, sometimes partitioning is.
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2011-08-15 23:15:47 | Re: backup-strategies for large databases |
Previous Message | MirrorX | 2011-08-15 23:06:39 | Re: backup-strategies for large databases |