Subject: Re: Barman WAL size issue
To: pgsql-admin@lists.postgresql.org
References: 
 <CAAV2-mXX8Neviye_FT-VS5dPt9RAz1nWjWuEBe=XGxjaoOwAnA@mail.gmail.com>
 <CAGDYbUP2Jb4=xAyRVXxqzeDVi4R1gooEOv78v=XgLp9SMcBjFw@mail.gmail.com>
 <CAAV2-mW6GoLRpY9-pVf+_f-oPE5+QWK0+C8jZq9wVd_4rHxjqg@mail.gmail.com>
 <9700d9ff-08f8-6730-69de-13806459c8d0@mnietz.de>
 <CAAV2-mVs-eXc8Sz7MOzjSKXP1eMQknUvp7-5TVHwt4u2kon9xg@mail.gmail.com>
 <CAAV2-mV-Xg=GGso+tOMYDhth-cJV_JRt9ucNZnUmyGv25hzDHQ@mail.gmail.com>
 <709645236.4282327.1511994923979@mail.yahoo.com>
From: Marco Nietz <pg@mnietz.de>
Message-ID: <4823dcac-7607-4dcd-37e2-568799eb74f9@mnietz.de>
Date: Thu, 30 Nov 2017 07:54:40 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <709645236.4282327.1511994923979@mail.yahoo.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: de-DE
Content-Transfer-Encoding: 8bit
Precedence: bulk

Information to unsubscribe can be found here:

https://wiki.postgresql.org/wiki/PGLister_Announce


Am 29.11.2017 um 23:35 schrieb Sean G:
> why are we getting these emails?
> how can we unsubscribe from this list?
> 
> suddenly these emails started to come into my email account and I could 
> not find a way to unsubscribe??????
> 
> this is against the law to get emails without any link to unsubscribe 
> from the emails.
> 
> 
> 
> 
> 
> On Wednesday, November 29, 2017, 5:59:02 AM EST, Günce Kaya 
> <guncekaya14@gmail.com> wrote:
> 
> 
> Hi Marco,
> 
> Backup process complete successfully. Now, WAL Size: 3.3 GiB. Everything 
> seems fine.
> 
> Thank you again for your helps.
> 
> Regards,
> Gunce
> 
> On Wed, Nov 29, 2017 at 10:29 AM, Günce Kaya <guncekaya14@gmail.com 
> <mailto:guncekaya14@gmail.com>> wrote:
> 
>     Hi Marco,
> 
>     Sorry for delay. I just want to see what's gonna happen in next
>     backup process. We use archiving via archive_command that includes
>     rsync. I checked log file and I did not faced any error about
>     archive_command or rsync process. Current backup still continuous.
>     Backup process takes long time and I'm gonna look at barman
>     list-backup command and I'll share if still continued this problem.
> 
>     Thank you for your helps.
> 
>     Regards,
>     Gunce
> 
>     On Tue, Nov 28, 2017 at 2:43 PM, Marco Nietz <pg@mnietz.de
>     <mailto:pg@mnietz.de>> wrote:
> 
>         Hi,
> 
>         which wal method are you using? Wal Streaming or archiving by
>         using archive_command?
> 
>         In case of streaming, you could check if receive-wal process is
>         running on the backup host and connected to the barman
>         replication slot on the postgresql server.
> 
>         In the other case, check your postgresql logfile if you have
>         errors about the archiving.
> 
> 
>         Greetings,
>         Marco
> 
> 
> 
>         Am 28.11.2017 um 11:51 schrieb Günce Kaya:
> 
>             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@gmail.com <mailto:shreeyansh2014@gmail.com>
>             <mailto:shreeyansh2014@gmail.c om
>             <mailto:shreeyansh2014@gmail.com>>> wrote:
> 
> 
> 
>                  On Tue, Nov 28, 2017 at 2:47 PM, Günce Kaya
>             <guncekaya14@gmail.com <mailto:guncekaya14@gmail.com>
>                  <mailto:guncekaya14@gmail.com
>             <mailto:guncekaya14@gmail.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/gu ncekaya
>             <https://tr.linkedin.com/in/guncekaya>> - Twitter
>                      <https://twitter.com/gguncesi>  - Blog
>                      <http://www.guncekaya.blogspot .com.tr/
>             <http://www.guncekaya.blogspot.com.tr/>>
> 
> 
> 
> 
>                  -- http://www.shreeyansh.com <http://www.shreeyansh.com>
> 
> 
> 
> 
>             -- 
>             Gunce Kaya
> 
>             Linkedin <https://tr.linkedin.com/in/gu ncekaya
>             <https://tr.linkedin.com/in/guncekaya>> - Twitter
>             <https://twitter.com/gguncesi>  - Blog
>             <http://www.guncekaya.blogspot .com.tr/
>             <http://www.guncekaya.blogspot.com.tr/>>
> 
> 
> 
> 
> 
>     -- 
>     Gunce Kaya
> 
>     Linkedin <https://tr.linkedin.com/in/guncekaya> - Twitter
>     <https://twitter.com/gguncesi> - Blog
>     <http://www.guncekaya.blogspot.com.tr/>
> 
> 
> 
> 
> -- 
> Gunce Kaya
> 
> Linkedin <https://tr.linkedin.com/in/guncekaya> - Twitter 
> <https://twitter.com/gguncesi> - Blog 
> <http://www.guncekaya.blogspot.com.tr/>