Re: stale WAL files?

From: Rene Romero Benavides <rene(dot)romero(dot)b(at)gmail(dot)com>
To: Rob Sargent <robjsargent(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: stale WAL files?
Date: 2019-04-03 23:23:10
Message-ID: CANaGW08JENvLoxKJ1LPUtkZ_p1A8-XzdKy=Oq0FSe1Ve+AaV0Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Apr 3, 2019 at 1:05 PM Rob Sargent <robjsargent(at)gmail(dot)com> wrote:

>
>
> On Apr 1, 2019, at 9:20 PM, Rene Romero Benavides <rene(dot)romero(dot)b(at)gmail(dot)com>
> wrote:
>
>
> On Mon, Apr 1, 2019 at 6:30 PM Rene Romero Benavides <
> rene(dot)romero(dot)b(at)gmail(dot)com> wrote:
>
>>
>> On Sat, Mar 30, 2019 at 5:03 PM Gmail <robjsargent(at)gmail(dot)com> wrote:
>>
>>>
>>>
>>> > On Mar 30, 2019, at 10:54 AM, Gmail <robjsargent(at)gmail(dot)com> wrote:
>>> >
>>> >
>>> >>>> On Mar 29, 2019, at 6:58 AM, Michael Paquier <michael(at)paquier(dot)xyz>
>>> wrote:
>>> >>>
>>> >>> On Thu, Mar 28, 2019 at 09:53:16AM -0600, Rob Sargent wrote:
>>> >>> This is pg10 so it's pg_wal. ls -ltr
>>> >>>
>>> >>>
>>> >>> -rw-------. 1 postgres postgres 16777216 Mar 16 16:33
>>> >>> 0000000100000CEA000000B1
>>> >>> -rw-------. 1 postgres postgres 16777216 Mar 16 16:33
>>> >>> 0000000100000CEA000000B2
>>> >>>
>>> >>> ... 217 more on through to ...
>>> >>>
>>> >>> -rw-------. 1 postgres postgres 16777216 Mar 16 17:01
>>> >>> 0000000100000CEA000000E8
>>> >>> -rw-------. 1 postgres postgres 16777216 Mar 16 17:01
>>> >>> 0000000100000CEA000000E9
>>> >>> -rw-------. 1 postgres postgres 16777216 Mar 28 09:46
>>> >>> 0000000100000CEA0000000E
>>> > I’m now down to 208 Mar 16 WAL files so they are being processed (at
>>> least deleted). I’ve taken a snapshot of the pg_wal dir such that I can
>>> see which files get processed. It’s none of the files I’ve listed previously
>>>
>>> Two more have been cleaned up. 001C and 001D generated at 16:38 Mar 16
>>>
>>>
>>>
>>> Please share your complete postgresql.conf file and the results from
>> this query:
>> SELECT * FROM pg_settings;
>> has someone in the past configured wal archiving?
>> You've ran out of disk space as this log message you shared states:
>> No space left on device
>> what's the output of df -h
>>
>> --
>> El genio es 1% inspiración y 99% transpiración.
>> Thomas Alva Edison
>> http://pglearn.blogspot.mx/
>>
>>
> BTW , how spread apart are checkpoints happening? do you have stats on
> that? maybe they're too spread apart and that's why WAL files cannot be
> recycled rapidly enough?
> --
> El genio es 1% inspiración y 99% transpiración.
> Thomas Alva Edison
> http://pglearn.blogspot.mx/
>
> two attempts (one in-line, one with attachement) at sending
> postgresql.conf and pg_settings report have been sent to a moderator.
>
>
>
As per your configuration :
max_wal_size = 50GB
this seems to be the cause for the WAL files piling up.

this has been declared twice, the last one is taking effect.
--
El genio es 1% inspiración y 99% transpiración.
Thomas Alva Edison
http://pglearn.blogspot.mx/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2019-04-04 00:10:04 Re: Seeded Replication
Previous Message Ron 2019-04-03 20:52:16 Re: Recommendation to run vacuum FULL in parallel