| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
| Cc: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Incremental backup with RSYNC or something? |
| Date: | 2011-11-18 06:47:21 |
| Message-ID: | CAOR=d=0o+O05Zm2gQu2k1Ko1cXOgcQXotkuSObxYoVvX6yaH4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Nov 13, 2011 at 7:01 AM, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> wrote:
>
> On Nov 13, 2011 7:39 PM, "Phoenix Kiula"
>
>> Searching google leads to complex things like "incremental WAL" and
>> whatnot, or talks of stuff like pgcluster. I'm hoping there's a more
>> straightforward core solution without additional software or PHD
>> degrees.
>
> Nothing really basic. You'll need to use PITR (WAL shipping), streaming
> replication or a row level replication solution.
One method they could use would be to partition the data into old and
new, and backup the new, then merge the partitions and start a new one
or something like that. But that's a huge pain. I would suggest PITR
backups here as the likely best match.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mamatha_Kagathi_Chan | 2011-11-18 07:01:19 | pg_dump error |
| Previous Message | Andrew Sullivan | 2011-11-18 06:37:01 | Re: Result of ORDER-BY |