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 20274.1145123863@sss.pgh.pa.us
Whole thread Raw
In response to Re: Proposed doc-patch: Identifying the Current WAL file  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Proposed doc-patch: Identifying the Current WAL file  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Proposed doc-patch: Identifying the Current WAL file  (Jeff Frost <jeff@frostconsultingllc.com>)
List pgsql-docs
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Also, what happens if the log switch happens, and some data change is
> written to the new WAL file in the first second, but nothing happens to
> the database after that for a minute?  Your test would still show the
> old log file.

You seem to be assuming that ls will sort on the basis of the truncated
mtime that it displays, which is not the actual behavior of ls AFAIK.

            regards, tom lane

pgsql-docs by date:

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