Re: standby not cleaning up WAL files often enough - Mailing list pgsql-admin

From Jeff Frost
Subject Re: standby not cleaning up WAL files often enough
Date
Msg-id F05A2C84-38CF-44E8-9AFC-FFB3E429E5E6@pgexperts.com
Whole thread Raw
In response to Re: standby not cleaning up WAL files often enough  (Jorge Torralba <jorge.torralba@gmail.com>)
List pgsql-admin
Like I mentioned before, it’s the *replica* not the primary. I.e. it’s not archiving. There are no cascaded replicas getting their WAL stream from it either.


postgres=# show wal_keep_segments ;
 wal_keep_segments
-------------------
 0
(1 row)



On Apr 22, 2015, at 5:08 PM, Jorge Torralba <jorge.torralba@gmail.com> wrote:

More of statng the obvious here :)

Make sure your archive directory is mounted or accessible from the DB server.

Check your wal_keep_segments. I cant imagine them being 3000 but you never know.

are you running synchronous or asynchronous replication?

JT

On Wed, Apr 22, 2015 at 5:02 PM, Jeff Frost <jeff@pgexperts.com> wrote:
It’s a good question, but I’m actually not talking about the WAL files in the archive (those are on S3), I’m talking about the WAL files in the pg_xlog directory.

> On Apr 22, 2015, at 5:00 PM, Jorge Torralba <jorge.torralba@gmail.com> wrote:
>
> Stupid question but it needs to be asked.
>
> Do you have this in your recovery.conf file ?
>
> archive_cleanup_command = 'pg_archivecleanup path to archived files %r’




--
Thanks,

Jorge Torralba
----------------------------

Note: This communication may contain privileged or other confidential information. If you are not the intended recipient, please do not print, copy, retransmit, disseminate or otherwise use the information. Please indicate to the sender that you have received this email in error and delete the copy you received. Thank You.

---
Jeff Frost <jeff@pgexperts.com>
CTO, PostgreSQL Experts, Inc.
Phone: 1-888-PG-EXPRT x506
FAX: 415-762-5122



pgsql-admin by date:

Previous
From: Jorge Torralba
Date:
Subject: Re: standby not cleaning up WAL files often enough
Next
From: danny
Date:
Subject: server doesn't listen postgresql 9.1 after service change