Re: stale WAL files?

From: Gmail <robjsargent(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: 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-03-30 23:03:28
Message-ID: 6F2111AD-1CD9-4077-AA8B-F6E1F7AD809D@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Samuel Williams 2019-03-31 03:31:51 Re: libpq read/write
Previous Message Tom Lane 2019-03-30 21:16:08 Re: CVE-2019-9193 about COPY FROM/TO PROGRAM