pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Richard Huxton <dev@archonet.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Proposed doc-patch: Identifying the Current WAL file
Date: Fri, 14 Apr 2006 11:44:56 -0400 (EDT)
Message-ID: <200604141544.k3EFiuw20847@candle.pha.pa.us> (raw)
In-Reply-To: <443E832D.30405@archonet.com>

Richard Huxton wrote:
> Reading Tom's posting here:
> http://archives.postgresql.org/pgsql-general/2006-04/msg00499.php
> 
> I just realised we don't seem to mention this in the docs anywhere. I
> propose adding a short paragraph to 23.3.1
> http://www.postgresql.org/docs/8.1/static/backup-online.html#BACKUP-ONLINE-CAVEATS
> 
> After "Except in the case of retrying a failure, it will be called only
> once for any given file name."
> 
> To identify the current, partially-filled WAL segment, sort first by
> mtime and second by file name. That is, take the latest mtime among the
> properly-named files, breaking ties by taking the higher filename.

I am confused by this.  Why do both mtime and file name need to be
checked?

-- 
  Bruce Momjian   http://candle.pha.pa.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +



view thread (27+ messages)  latest in thread

Message-ID: <200604141544.k3EFiuw20847@candle.pha.pa.us>
Permalink:  ../200604141544.k3EFiuw20847@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200604141544.k3EFiuw20847@candle.pha.pa.us

 · 

reply

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: pgman@candle.pha.pa.us, dev@archonet.com
  Subject: Re: Proposed doc-patch: Identifying the Current WAL file
  In-Reply-To: <200604141544.k3EFiuw20847@candle.pha.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