[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] Recovery_target_time misinterpreted?
From:       Klaus Ita <koki.eml () gmail ! com>
Date:       2013-07-31 14:59:50
Message-ID: CAK9oVJyP48F_R5r-NZ3nkchvT4bCruusEr-7aMmcum8=LhPOdA () mail ! gmail ! com
[Download RAW message or body]

2013-07-30 11:15:15 UTC <%> LOG:  starting point-in-time recovery to
2013-07-27 21:20:17.127664+00
2013-07-30 11:15:15 UTC <%> LOG:  restored log file
"00000001000002300000005C" from archive
2013-07-30 11:15:15 UTC <%> LOG:  restored log file
"00000001000002300000005A" from archive
2013-07-30 11:15:15 UTC <%> LOG:  redo starts at 230/5ACD7CC0
...
...
...
2013-07-30 14:28:45 UTC <%> LOG:  restored log file
"000000010000026400000002" from archive
2013-07-30 14:28:45 UTC <%> LOG:  unexpected pageaddr 263/C706C000 in log
file 612, segment 2, offset 442368
2013-07-30 14:28:45 UTC <%> LOG:  redo done at 264/20698A8
2013-07-30 14:28:45 UTC <%> LOG:  last completed transaction was at log
time 2013-07-18 11:42:22.121512+00
2013-07-30 14:28:45 UTC <%> LOG:  restored log file
"000000010000026400000002" from archive
cp: cannot stat
`/var/tmp/xlogs_recovered_2013-07-30/wal_files/00000002.history*': No such
file or directory
mv: cannot stat `/tmp/00000002.history': No such file or directory
2013-07-30 14:28:45 UTC <%> LOG:  selected new timeline ID: 2
cp: cannot stat
`/var/tmp/xlogs_recovered_2013-07-30/wal_files/00000001.history*': No such
file or directory
mv: cannot stat `/tmp/00000001.history': No such file or directory
2013-07-30 14:28:45 UTC <%> LOG:  archive recovery complete
2013-07-30 14:29:09 UTC <%> LOG:  autovacuum launcher started
2013-07-30 14:29:09 UTC <%> LOG:  database system is ready to accept
connections


well, that does not indicate anything for me.



On Wed, Jul 31, 2013 at 9:37 AM, Albe Laurenz <laurenz.albe@wien.gv.at>wrote:

> Klaus Ita wrote:
> > I have restored a Database Cluster with a recovery_target_time set to
> >
> > recovery_target_time =  '2013-07-27 21:20:17.127664+00'
> > recovery_target_inclusive = false
> >
> >
> >
> > now it seems the restore rather restored to some point in time (rather
> the 18th than the 27th). Is
> > there an explanation for this huge gap? Is that the last 'consistent
> state'?
>
> Maybe the log entries created during restore can answer the question.
>
> Yours,
> Laurenz Albe
>

[Attachment #3 (text/html)]

<div dir="ltr"><div>2013-07-30 11:15:15 UTC &lt;%&gt; LOG:   starting point-in-time \
recovery to 2013-07-27 21:20:17.127664+00<br>2013-07-30 11:15:15 UTC &lt;%&gt; LOG:   \
restored log file &quot;00000001000002300000005C&quot; from archive<br> 2013-07-30 \
11:15:15 UTC &lt;%&gt; LOG:   restored log file &quot;00000001000002300000005A&quot; \
from archive<br>2013-07-30 11:15:15 UTC &lt;%&gt; LOG:   redo starts at \
230/5ACD7CC0<br>...<br>...<br>...<br>2013-07-30 14:28:45 UTC &lt;%&gt; LOG:   \
restored log file &quot;000000010000026400000002&quot; from archive<br> 2013-07-30 \
14:28:45 UTC &lt;%&gt; LOG:   unexpected pageaddr 263/C706C000 in log file 612, \
segment 2, offset 442368<br>2013-07-30 14:28:45 UTC &lt;%&gt; LOG:   redo done at \
264/20698A8<br>2013-07-30 14:28:45 UTC &lt;%&gt; LOG:   last completed transaction \
was at log time 2013-07-18 11:42:22.121512+00<br> 2013-07-30 14:28:45 UTC &lt;%&gt; \
LOG:   restored log file &quot;000000010000026400000002&quot; from archive<br>cp: \
cannot stat `/var/tmp/xlogs_recovered_2013-07-30/wal_files/00000002.history*&#39;: No \
                such file or directory<br>
mv: cannot stat `/tmp/00000002.history&#39;: No such file or directory<br>2013-07-30 \
14:28:45 UTC &lt;%&gt; LOG:   selected new timeline ID: 2<br>cp: cannot stat \
`/var/tmp/xlogs_recovered_2013-07-30/wal_files/00000001.history*&#39;: No such file \
                or directory<br>
mv: cannot stat `/tmp/00000001.history&#39;: No such file or directory<br>2013-07-30 \
14:28:45 UTC &lt;%&gt; LOG:   archive recovery complete<br>2013-07-30 14:29:09 UTC \
&lt;%&gt; LOG:   autovacuum launcher started<br>2013-07-30 14:29:09 UTC &lt;%&gt; \
LOG:   database system is ready to accept connections<br> <br><br></div>well, that \
does not indicate anything for me.<br><div><br></div></div><div \
class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 31, 2013 at 9:37 AM, \
Albe Laurenz <span dir="ltr">&lt;<a href="mailto:laurenz.albe@wien.gv.at" \
target="_blank">laurenz.albe@wien.gv.at</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div class="im">Klaus Ita wrote:<br> &gt; I have restored a \
Database Cluster with a recovery_target_time set to<br> &gt;<br>
&gt; recovery_target_time =   &#39;2013-07-27 21:20:17.127664+00&#39;<br>
&gt; recovery_target_inclusive = false<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; now it seems the restore rather restored to some point in time (rather the 18th \
than the 27th). Is<br> &gt; there an explanation for this huge gap? Is that the last \
&#39;consistent state&#39;?<br> <br>
</div>Maybe the log entries created during restore can answer the question.<br>
<br>
Yours,<br>
Laurenz Albe<br>
</blockquote></div><br></div>



[prev in list] [next in list] [prev in thread] [next in thread]