Re: Proposed doc-patch: Identifying the Current WAL file - Mailing list pgsql-docs

From Tom Lane
Subject Re: Proposed doc-patch: Identifying the Current WAL file
Date
Msg-id 20245.1145123792@sss.pgh.pa.us
Whole thread Raw
In response to Re: Proposed doc-patch: Identifying the Current WAL file  (Jeff Frost <jeff@frostconsultingllc.com>)
List pgsql-docs
Jeff Frost <jeff@frostconsultingllc.com> writes:
>>> ls -tp /pg_xlog/ | grep -v "backup\|/" | head -1
>>
>> What does the -p and \| pipe check do?  We don't have named pipes in
>> that directory, do we?

> The -p shows forward slashes after directories and the \| acts as an or and
> the / following that just lets us filter directories out.

This seems both overly cute and wrong, because it fails to filter plain
files that might have a new mtime but aren't WAL files.  I'd suggest a
simple test on file name to make sure it looks like a WAL file, ie,
24 hex digits.

    ls -t .../pg_xlog | grep
'^[0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F]$'
|head -1 

            regards, tom lane

pgsql-docs by date:

Previous
From: Jeff Frost
Date:
Subject: Re: Proposed doc-patch: Identifying the Current WAL file
Next
From: Tom Lane
Date:
Subject: Re: Proposed doc-patch: Identifying the Current WAL file