From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Imre Oolberg <imre@auul.pri.ee>
To: pgsql-admin@postgresql.org
Subject: Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal
Date: Mon, 03 Jan 2011 11:36:14 -0600
Message-ID: <4D21B4AE0200002500038F48@gw.wicourts.gov> (raw)
In-Reply-To: <4D21AC15.1010102@auul.pri.ee>
References: <4D1C670E.1090408@auul.pri.ee>
<4D21AC15.1010102@auul.pri.ee>
Imre Oolberg <imre@auul.pri.ee> wrote:
> archive_command = 'test ! -f
> /data/backup/postgresql/archive-logs/%f &&
> cp %p /data/backup/postgresql/archive-logs'
I suppose that will work, but why not specify %f in the copy target?
> I guess that my problem is probably that although my .backup file
> says
>
> 000000010000000000000009.00000020.backup
> START WAL LOCATION: 0/9000020 (file 000000010000000000000009)
> STOP WAL LOCATION: 1/6325B2E0 (file 000000010000000100000063)
> CHECKPOINT LOCATION: 0/A2C4908
> START TIME: 2011-01-03 11:32:17 EET
> LABEL: test
> STOP TIME: 2011-01-03 12:18:27 EET
>
> looking at the pg_ctl.log it starts reading wal logs beginning
> with 000000010000000100000063 and not with
> 000000010000000000000009
What did you have in your recovery.conf file?
-Kevin
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, imre@auul.pri.ee
Subject: Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal
In-Reply-To: <4D21B4AE0200002500038F48@gw.wicourts.gov>
References: <4D1C670E.1090408@auul.pri.ee> <4D21AC15.1010102@auul.pri.ee> <4D21B4AE0200002500038F48@gw.wicourts.gov>
* 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