From: | Richard <husttripper(at)vip(dot)sina(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [HACKERS] Online backup cause boot failure, anyone know why? |
Date: | 2010-08-05 13:50:16 |
Message-ID: | 201008052150153590583@vip.sina.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I reboot PG because I found PG recovery end point if far away from the actual end point of the XLOG on the backup directory, so I want to test if the original DB is OK.
Unfortunately, I got the same PG log on the original DB. I don't unstand what you said, I missing what?
------------------
Richard
2010-08-05
-------------------------------------------------------------
发件人:Andrew Dunstan
发送日期:2010-08-05 21:40:13
收件人:Richard
抄送:pgsql-hackers
主题:Re: [HACKERS] Online backup cause boot failure, anyone know why?
On 08/05/2010 09:19 AM, Richard wrote:
> I want to create a database backup when PG is running, so I call pg_start_backup(''), scp the data to a backup directory, pg_stop_backup.
> Then I reboot PG , PG boot failed with log like "unexpected pageaddr X/X in log file X, segment X, offset X" "WAL ends before end time of backup dump".
> Then I check the failure XLOG file, found the error page contains a pageaddr 8K before it should be, and the failure XLOG record a ONLINE CHECKPONT with 60 bytes in former page, the other 4 bytes missing.
>
> Any one met this before? Please help me!
>
>
This question really belongs on the pgsql-general list, not the -hackers
list.
If all you copied was the data directory then you haven't done this
right anyway. See
<http://www.postgresql.org/docs/8.3/static/continuous-archiving.html#BACKUP-TIPS>
Why did you reboot postgres after taking your backup?
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Boxuan Zhai | 2010-08-05 13:55:29 | Re: MERGE Specification |
Previous Message | Kevin Grittner | 2010-08-05 13:44:19 | Re: ECPG dynamic cursor fix for UPDATE/DELETE ... WHERE CURRENT OF :curname |