Re: Maximum number of WAL files in the pg_xlog directory

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Maximum number of WAL files in the pg_xlog directory
Date: 2014-10-15 21:17:53
Message-ID: CAECtzeXVaMpF2XJoAnDFjP1eMGCzmoLGfu7tvytjOW59FuQFsw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2014-10-15 23:12 GMT+02:00 Josh Berkus <josh(at)agliodbs(dot)com>:

> On 10/15/2014 01:25 PM, Guillaume Lelarge wrote:
> > Monitoring is another matter, and I don't really think a monitoring
> > solution should count the WAL files. What actually really matters is the
> > database availability, and that is covered with having enough disk space
> in
> > the WALs partition.
>
> If we don't count the WAL files, though, that eliminates the best way to
> detecting when archiving is failing.
>
>
WAL files don't give you this directly. You may think it's an issue to get
a lot of WAL files, but it can just be a spike of changes. Counting .ready
files makes more sense when you're trying to see if wal archiving is
failing. And now, using pg_stat_archiver is the way to go (thanks Gabriele
:) ).

--
Guillaume.
http://blog.guillaume.lelarge.info
http://www.dalibo.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2014-10-15 21:19:23 Re: Maximum number of WAL files in the pg_xlog directory
Previous Message Josh Berkus 2014-10-15 21:12:36 Re: Maximum number of WAL files in the pg_xlog directory