From: | Bèrto ëd Sèra <berto(dot)d(dot)sera(at)gmail(dot)com> |
---|---|
To: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
Cc: | hamann(dot)w(at)t-online(dot)de, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: incremental dumps |
Date: | 2013-08-01 13:20:26 |
Message-ID: | CAKwGa_97Bkq_iNOMW7x4L_yW641EP9Ns0aAfYukytb4MUpChwA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> suppose wal archiving or PITR would be better
+1, never re-invent the wheel, unless you really need to.
Bèrto
On 1 August 2013 14:14, Luca Ferrari <fluca1978(at)infinito(dot)it> wrote:
> On Thu, Aug 1, 2013 at 10:59 AM, <hamann(dot)w(at)t-online(dot)de> wrote:
>
> > However, the diff files seem to be considerably larger than one would
> expect.
> > One obvious part of the problem is the fact that diff shows old and new
> text,
> > so e.g. changing the amount of stock for a product with a 1kB description
> > would generate at least 2kb of text in the diff file.
> >
> > What would be a better approach?
>
> I suppose wal archiving or PITR would be better, but assuming you want
> text files I guess you need to change your database structure to
> either:
> 1) include a watermark on data and dump only data since the last dump
> (to do manually);
> 2) partition your tables and backup specific tables/partitions
> depending on the timing.
>
> Hope this helps.
> Luca
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
==============================
If Pac-Man had affected us as kids, we'd all be running around in a
darkened room munching pills and listening to repetitive music.
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Collins | 2013-08-01 13:24:13 | Re: incremental dumps |
Previous Message | Luca Ferrari | 2013-08-01 13:14:01 | Re: incremental dumps |