What to do when pg_xlog directory has filled up the filesystem

From: John Scalia <jayknowsunix(at)gmail(dot)com>
To: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: What to do when pg_xlog directory has filled up the filesystem
Date: 2015-01-23 16:00:31
Message-ID: 54C2701F.1020505@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi all,

Just curious about this issue as it has occurred on my 9.4.0 sandbox primary server. The link to the directory specified in archive_command had disappeared, so the command
specified in archive_command kept failing overnight. This resulted in many WAL segments piling up in the pg_xlog directory and a bunch of <wal name>.ready files appearing in the
pg_xlog/archive.status directory. The filesystem had reached 100% full so the database quit and would not restart. I've thought about just moving some of the WAL segments
temporarily to another filesystem, but which ones, oldest or newest? And is that really the best way to deal with this or what is the best way to deal with this kind of issue?
--
Jay

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Jeff Frost 2015-01-23 16:33:21 Re: What to do when pg_xlog directory has filled up the filesystem
Previous Message Khangelani Gama 2015-01-23 08:54:43 Re: PostgreSQL 9.2.4 - please assist with the query