[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] incremental dumps
From:       Bèrto ëd Sèra <berto.d.sera () gmail ! com>
Date:       2013-08-01 13:20:26
Message-ID: CAKwGa_97Bkq_iNOMW7x4L_yW641EP9Ns0aAfYukytb4MUpChwA () mail ! gmail ! com
[Download RAW message or body]

> 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@infinito.it> wrote:

> On Thu, Aug 1, 2013 at 10:59 AM,  <hamann.w@t-online.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@postgresql.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.

[Attachment #3 (text/html)]

<div dir="ltr">&gt;<span \
style="font-family:arial,sans-serif;font-size:12.800000190734863px">  suppose wal \
archiving or PITR would be better<br>+1, never re-invent the wheel, unless you really \
need to.  </span><div><span \
style="font-family:arial,sans-serif;font-size:12.800000190734863px"><br> \
</span></div><div><span \
style="font-family:arial,sans-serif;font-size:12.800000190734863px">Bèrto</span></div></div><div \
class="gmail_extra"><br><br><div class="gmail_quote">On 1 August 2013 14:14, Luca \
Ferrari <span dir="ltr">&lt;<a href="mailto:fluca1978@infinito.it" \
target="_blank">fluca1978@infinito.it</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div class="im">On Thu, Aug 1, 2013 at 10:59 AM,   &lt;<a \
href="mailto:hamann.w@t-online.de">hamann.w@t-online.de</a>&gt; wrote:<br>

<br>
&gt; However, the diff files seem to be considerably larger than one would \
expect.<br> &gt; One obvious part of the problem is the fact that diff shows old and \
new text,<br> &gt; so e.g. changing the amount of stock for a product with a 1kB \
description<br> &gt; would generate at least 2kb of text in the diff file.<br>
&gt;<br>
&gt; What would be a better approach?<br>
<br>
</div>I suppose wal archiving or PITR would be better, but assuming you want<br>
text files I guess you need to change your database structure to<br>
either:<br>
1) include a watermark on data and dump only data since the last dump<br>
(to do manually);<br>
2) partition your tables and backup specific tables/partitions<br>
depending on the timing.<br>
<br>
Hope this helps.<br>
<span class="HOEnZb"><font color="#888888">Luca<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
--<br>
Sent via pgsql-general mailing list (<a \
href="mailto:pgsql-general@postgresql.org">pgsql-general@postgresql.org</a>)<br> To \
make changes to your subscription:<br> <a \
href="http://www.postgresql.org/mailpref/pgsql-general" \
target="_blank">http://www.postgresql.org/mailpref/pgsql-general</a><br> \
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- \
<br>==============================<br><span \
style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:12px;line-height:17px">If \
Pac-Man had affected us as kids, we&#39;d all be running around in a darkened room \
munching pills and listening to repetitive music.</span> </div>



[prev in list] [next in list] [prev in thread] [next in thread]