From: | Günce Kaya <guncekaya14(at)gmail(dot)com> |
---|---|
To: | Shreeyansh Dba <shreeyansh2014(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Barman WAL size issue |
Date: | 2017-11-28 10:51:10 |
Message-ID: | CAAV2-mW6GoLRpY9-pVf+_f-oPE5+QWK0+C8jZq9wVd_4rHxjqg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello,
There are some cron which execute insert, update statement daily. It's not
possible nothing happened after previous backup. So, do you have another
idea about that?
Regards,
Gunce
On Tue, Nov 28, 2017 at 12:44 PM, Shreeyansh Dba <shreeyansh2014(at)gmail(dot)com>
wrote:
>
>
> On Tue, Nov 28, 2017 at 2:47 PM, Günce Kaya <guncekaya14(at)gmail(dot)com> wrote:
>
>> Hi all,
>>
>> We use Barman for backup. I checked latest backup as to whether having
>> latest backup is success and I saw WAL size is 0 B.
>>
>> -bash-4.1$ barman list-backup dbalpha
>> dbalpha 20171127T190002 - Tue Nov 28 09:43:40 2017 - Size: 326.0 GiB -
>> WAL Size: 0 B ....
>>
>> I think it's not normal. Any help would be appreciated.
>>
>
> This is quite normal scenario, I suspect as not many transactions have
> happened since its previous backup was taken which resulted in WAL size to
> 0 B
>
>>
>> Regards,
>> Gunce Kaya
>>
>> Linkedin <https://tr.linkedin.com/in/guncekaya> - Twitter
>> <https://twitter.com/gguncesi> - Blog
>> <http://www.guncekaya.blogspot.com.tr/>
>>
>
>
>
> --
> [image: http://www.shreeyansh.com] <http://www.shreeyansh.com>
>
--
Gunce Kaya
Linkedin <https://tr.linkedin.com/in/guncekaya> - Twitter
<https://twitter.com/gguncesi> - Blog
<http://www.guncekaya.blogspot.com.tr/>
From | Date | Subject | |
---|---|---|---|
Next Message | Marco Nietz | 2017-11-28 12:43:02 | Re: Barman WAL size issue |
Previous Message | Shreeyansh Dba | 2017-11-28 10:44:26 | Re: Barman WAL size issue |