Re: error during PITR

is it possible that the timestamp that you put there ('2011-12-22
07:27:08') is before the time that you issued the command pg_stop_backup?
you can check that by looking at the backup.label file where is says when
the backup was finished.

you can only use point in time recovery after the point when you issued the
pg_stop_backup command and the backup was finished b/c up to that point you
need to recover all the relevant wal archives to bring your database into a
consistent mode. after that point you can stop at any time since the db is
already consistent.

On Thu, Dec 22, 2011 at 12:11 PM, Karuna Karpe [via PostgreSQL] <
ml-node+s1045698n5094221h64(at)n5(dot)nabble(dot)com> wrote:

> Hello,
>
>
> I doing PITR using following doc.
>
> http://www.mkyong.com/database/postgresql-point-in-time-recovery-incremental-backup/
>
> But when I am doing recovery till the specific time so I change parameter
> in recover.conf file.
> i.e. restore_command = 'cp /opt/PostgresPlus/archive/%f %p'
> recovery_target_time = '2011-12-22 07:27:08'
>
> when I restart ppas 9.0 server then I got following error: (this is in log
> file)
>
> LOG: database system was shut down at 2011-12-22 08:21:11 IST
> LOG: starting point-in-time recovery to 2011-12-22 07:27:08+05:30
> LOG: restored log file "000000010000000000000014" from archive
> LOG: redo starts at 0/14000070
> LOG: restored log file "000000010000000000000015" from archive
> LOG: restored log file "000000010000000000000016" from archive
> LOG: restored log file "000000010000000000000017" from archive
> LOG: restored log file "000000010000000000000018" from archive
> LOG: restored log file "000000010000000000000019" from archive
> LOG: recovery stopping before commit of transaction 756, time 2011-12-22
> 07:29:08.152325+05:30
> LOG: redo done at 0/2423F264
> LOG: last completed transaction was at log time 2011-12-22
> 07:26:51.427245+05:30
> FATAL: requested recovery stop point is before consistent recovery point
> LOG: startup process (PID 5413) exited with exit code 1
>
>
> Please let me know what is going wrong in that?
> can any one please give me solution for this problem???
>
>
> Regards,
> Karuna Karpe.
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://postgresql.1045698.n5.nabble.com/error-during-PITR-tp5094221p5094221.html
> To start a new topic under PostgreSQL - admin, email
> ml-node+s1045698n2076596h89(at)n5(dot)nabble(dot)com
> To unsubscribe from PostgreSQL - admin, click here<http://postgresql.1045698.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2076596&code=bWlycm9yeEBnbWFpbC5jb218MjA3NjU5NnwtMjExNTQzMjE0Mg==>
> .
> NAML<http://postgresql.1045698.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.InstantMailNamespace&breadcrumbs=instant+emails%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>

--
View this message in context: http://postgresql.1045698.n5.nabble.com/error-during-PITR-tp5094221p5094532.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.