Re: Decreasing the data loss after failover - Mailing list pgsql-admin

From Craig James
Subject Re: Decreasing the data loss after failover
Date
Msg-id CAFwQ8rdno6oBD5-ouaAyvcvSROY62eeZ4-3NqEEZeKtU=Jw8qA@mail.gmail.com
Whole thread Raw
In response to Re: Decreasing the data loss after failover  (sinasaharkhiz <sinas1991@gmail.com>)
List pgsql-admin
On Sat, Jun 6, 2015 at 8:43 PM, sinasaharkhiz <sinas1991@gmail.com> wrote:
Yeah I just set the archive_timeout to 5 minutes. But I thought that would
make postgresql to generate more wal files than before. Because the wal
files would be switched before getting completely full. So that would make
more 16MB wal files with less than 16MB data, and that will increase the
size of my backup.
But after I changed archive_timeout and restarted the barman backup, it has
not increased. So I wonder if I'm thinking wrong about it or I have done
something wrong. Do you have any idea about this?

If the files are compressed, you will have more files, but the total size will be almost the same. Gzip compression reduces large sections of identical bytes to almost nothing.

For example, I just compressed a 750 MB file of zeros to 750 KB -- a 1000:1 compression ratio.

Craig




--
View this message in context: http://postgresql.nabble.com/Decreasing-the-data-loss-after-failover-tp5852659p5852817.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.


--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



--
---------------------------------
Craig A. James
Chief Technology Officer
eMolecules, Inc.
---------------------------------

pgsql-admin by date:

Previous
From: Keith
Date:
Subject: Re: Decreasing the data loss after failover
Next
From: "AL-Temimi, Muthana"
Date:
Subject: cache Memory