From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Niels Kristian Schjødt <nielskristian(at)autouncle(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org list" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: pg_xlog dir not getting swept |
Date: | 2016-06-29 19:19:50 |
Message-ID: | CAMkU=1xGbK9kOBjH9PEHYK1HZvAO8q53r6HGGMC=8Hg+PLg54Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Jun 29, 2016 at 3:00 AM, Niels Kristian Schjødt
<nielskristian(at)autouncle(dot)com> wrote:
> About a day ago, there seems to have been some trouble in the network of my
> database (postgresql 9.3).
>
> I’m running my db with a streaming replication setup with wall shipping.
>
> I sync wal logs to a mounted networkdrive using archive_command = 'rsync -a
> %p /mnt/wal_drive/wals/%f </dev/null’. Somehow this command was failing,
> leading to my pg_xlog dir building up (590Gb). I rebooted the server, and
> the archiving command seems to succeed now - however - After about an hour
> of running, the pg_xlog drive has not decreased in size - I would have
> expect that! I can see that lot’s of files get’s synced to the
> /mnt/wal_drive/wals dir, but somehow the pg_xlog dir is not swept (yet)?
> Will this happen automatically eventually, or do I need to do something
> manually?
Successfully archived files are only removed by the checkpointer. The
logic is quite complex and it can be very frustrating trying to
predict exactly when any given file will get removed. You might want
to run a few manual checkpoints to see if that cleans it up. But turn
on log_checkpoints and reload the configuration first.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-06-29 20:20:31 | Re: Random slow queries |
Previous Message | devel.brain99 | 2016-06-29 18:04:31 | Re: Random slow queries |