From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: incremental dumps |
Date: | 2013-08-05 09:44:09 |
Message-ID: | CAKoxK+5n49+LA11T44TwhGDqX-efiftOzjYAOKxbUP2QKdcsbQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Aug 2, 2013 at 6:55 PM, <hamann(dot)w(at)t-online(dot)de> wrote:
> thanks for the hint - this is probably one of the things to do.
> I have something else in mind, but at present I just suspect that this might happen:
> when I modify data and select _without an ordering_, I am pretty sure to get the data
> in a different sequence than before. So I wonder whethet forcing the dump to honor
> a particular ordering (if that is at all possible) would also reduce the size of dumps ... or the
> time diff takes to produce them
>
May I ask what is the final purpose? Because if it is to take a backup
I guess this is not the right way to go, while if it is keeping (and
rebuilding) an history of data, than using a more specific approach
(like logging) could give you less headaches.
Luca
From | Date | Subject | |
---|---|---|---|
Next Message | Krzysztof xaru Rajda | 2013-08-05 09:44:39 | [tsearch2] Problem with case sensitivity (or with creating own dictionary) |
Previous Message | KONDO Mitsumasa | 2013-08-05 09:40:10 | Re: Bottlenecks with large number of relation segment files |