Re: Unix Postgres 9.5. using pg_basebackup and WAL files. Can't get a PITR recovery

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: "Pruett, Jennis" <Jennis(dot)Pruett(at)leidos(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Unix Postgres 9.5. using pg_basebackup and WAL files. Can't get a PITR recovery
Date: 2016-07-20 15:03:47
Message-ID: CAMkU=1zP1AduVsyRQD1KXY7XYE=b1SB5ATey5Ed+TJgog4GuhA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jul 15, 2016 at 10:09 AM, Pruett, Jennis
<Jennis(dot)Pruett(at)leidos(dot)com> wrote:
> I can't cut and paste my issues, so I will explain as best I can.
>
>
>
> I’m testing PITR on a single 9.5 db (no replication setups).
>
>
>
> I have all the settings that I can find, wal_level, archive_command,
>
> restore_command, directories defined, logs defined. My WAL files are stored
> off in
>
> another area with gzip in the archive_command. The restore_command also uses
> gunzip. Those work fine.
>
> (pg_xresetlog seems to work OK too)
>
>
>
> I can restore from a pg_basebackup, but if I define PITR in recovery.conf
> along with the
>
> pg_basebackup in place, I can't get to that point in time.

What does the server log file say?

You should see something like this:

3071 2016-07-20 08:02:00.698 PDT LOG: database system was
interrupted; last known up at 2016-07-14 12:59:39 PDT
3071 2016-07-20 08:02:04.503 PDT LOG: starting point-in-time
recovery to 2016-07-19 13:50:00-07
3071 2016-07-20 08:02:04.872 PDT LOG: restored log file
"00000002.history" from archive

What do you see instead?

Cheers,

Jeff

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Melvin Davidson 2016-07-20 15:34:46 Re: Multiple clusters with same tablespace location
Previous Message Nate Dudenhoeffer 2016-07-20 14:59:23 Multiple clusters with same tablespace location