[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-admin
Subject:    Reducing the size or amount of WAL files on the master server
From:       Shane Archer <shane.archer () netgalley ! com>
Date:       2018-01-15 18:51:44
Message-ID: CAJkQgqcBCL59zzGWydF=KZdqv2Z1j6TqadODqexONENFiZq5tQ () mail ! gmail ! com
[Download RAW message or body]

On a master PostgreSQL 9.5 server, we consistently have 160-180GB of WAL
files being stored, which span a 6-7 day time period. I'd like to reduce
this so that we aren't using as much space, and also because we won't ever
need to recover that far into the past (we'd just restore a backup at that
point).

I've tried changing settings such as wal_keep_segments and max_wal_size but
they don't seem to have an effect, even after a full server restart. For
example, I've set max_wal_size to 256MB but the files themselves remain at
512MB.

Is there some part of the process I'm missing, or a setting?

[Attachment #3 (text/html)]

<div dir="ltr"><div>On a master PostgreSQL 9.5 server, we consistently have 160-180GB \
of WAL files being stored, which span a 6-7 day time period. I&#39;d like to reduce \
this so that we aren&#39;t using as much space, and also because we won&#39;t ever \
need to recover that far into the past (we&#39;d just restore a backup at that \
point).</div><div><br></div><div>I&#39;ve tried changing settings such as \
wal_keep_segments and max_wal_size but they don&#39;t seem to have an effect, even \
after a full server restart. For example, I&#39;ve set max_wal_size to 256MB but the \
files themselves remain at 512MB.</div><div><br></div><div>Is there some part of the \
process I&#39;m missing, or a setting?</div><div><br></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]