pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tom Davies <tgdavies@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: on-line backup questions
Date: Fri, 21 Dec 2007 21:33:50 -0500
Message-ID: <15488.1198290830@sss.pgh.pa.us> (raw)
In-Reply-To: <0FBA939C-2ED1-4400-BD3B-5290193837D0@gmail.com>
References: <0FBA939C-2ED1-4400-BD3B-5290193837D0@gmail.com>

Tom Davies <tgdavies@gmail.com> writes:
> 1. Purely out of curiousity, what's the nnnnnnnn.history file which is  
> requested from the archive when you restore?

Read the doc section about timelines --- if a history file exists,
it's needed to allow proper tracing of the "timeline" through multiple
recovery attempts.

> 3. What's the best thing to do when I deliberately shut down  
> PostgreSQL (i.e. pg_ctl stop)? When I start again I will be restoring  
> from the most recent backup and rolling forward over the archived WAL  
> files. I believe that shutdown leaves me with unarchived WAL files in  
> pg_xlog.

Yeah, you should archive the latest WAL file, but in 8.0 you'd have to
do that manually.  (IIRC there isn't even a forced-xlog-switch function
in that version to help you.)

> 4. I'm using PostgreSQL 8.0 -- are there any significant improvements  
> in on-line backups in later versions?

Get thyself onto 8.2 ASAP, or maybe go to 8.3 shortly after the
holidays.  8.0 is basically our stone age for PITR support; while
the concepts haven't changed since then, we've filed off a whole lot
of rough edges in operational details.  In a situation where you're
depending on archive recovery as much as this, you *need* those fixes.

			regards, tom lane



view thread (3+ messages)  latest in thread

Message-ID: <15488.1198290830@sss.pgh.pa.us>
Permalink:  ../15488.1198290830@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/15488.1198290830@sss.pgh.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-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, tgdavies@gmail.com
  Subject: Re: on-line backup questions
  In-Reply-To: <15488.1198290830@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