From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Jeff Frost <jeff@frostconsultingllc.com>
Cc: Richard Huxton <dev@archonet.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Proposed doc-patch: Identifying the Current WAL file
Date: Sat, 15 Apr 2006 13:57:43 -0400
Message-ID: <20274.1145123863@sss.pgh.pa.us> (raw)
In-Reply-To: <200604151726.k3FHQvI01801@candle.pha.pa.us>
References: <200604151726.k3FHQvI01801@candle.pha.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, jeff@frostconsultingllc.com, dev@archonet.com
Subject: Re: Proposed doc-patch: Identifying the Current WAL file
In-Reply-To: <20274.1145123863@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox