pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marco Nietz <pg@mnietz.de>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Barman WAL size issue
Date: Tue, 28 Nov 2017 13:43:02 +0100
Message-ID: <9700d9ff-08f8-6730-69de-13806459c8d0@mnietz.de> (raw)
In-Reply-To: <CAAV2-mW6GoLRpY9-pVf+_f-oPE5+QWK0+C8jZq9wVd_4rHxjqg@mail.gmail.com>
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>

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>> wrote:
> 
> 
> 
>     On Tue, Nov 28, 2017 at 2:47 PM, Günce Kaya <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/guncekaya> - Twitter
>         <https://twitter.com/gguncesi> - Blog
>         <http://www.guncekaya.blogspot.com.tr/;
> 
> 
> 
> 
>     -- 
>     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/;




view thread (8+ messages)  latest in thread

Message-ID: <9700d9ff-08f8-6730-69de-13806459c8d0@mnietz.de>
Permalink:  ../9700d9ff-08f8-6730-69de-13806459c8d0@mnietz.de/
Also on:    postgresql.org/message-id/9700d9ff-08f8-6730-69de-13806459c8d0@mnietz.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: pg@mnietz.de
  Subject: Re: Barman WAL size issue
  In-Reply-To: <9700d9ff-08f8-6730-69de-13806459c8d0@mnietz.de>
  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>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox