Online backup cause boot failure, anyone know why?
in [PgSql]
|
Prev: Earn more for a more satisfactory life. agonizing adelocodonic affrighted
Next: Online backup cause boot failure,anyone know why?
From: "Richard" on 5 Aug 2010 10:21 Thanks for replying. But I could't find relation between the RequestXLogSwitch function and the error I met. For perfromance purpose , I change the pg_start_backup checkpoint type from CHECKPOINT_WAIT to CHECKPOINT_IMMEDIATE, does it matter? ------------------ Richard 2010-08-05 ------------------------------------------------------------- �����ˣ�Tom Lane �������ڣ�2010-08-05 22:04:30 �ռ��ˣ�Richard ���ͣ�pgsql-hackers ���⣺Re: [HACKERS] Online backup cause boot failure, anyone know why? "Richard" <husttripper(a)vip.sina.com> writes: > PS : I am using PG 8.3.7 I believe there's a related bug fix in 8.3.8. BTW, -hackers is not the place for this type of question. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Richard" on 5 Aug 2010 10:56 I am sorry, my English is poor. I was confused by what you said. What do you mean by saying "that'd break it"! ------------------ Richard 2010-08-05 ------------------------------------------------------------- �����ˣ�Tom Lane �������ڣ�2010-08-05 22:44:50 �ռ��ˣ�Richard ���ͣ�pgsql-hackers ���⣺Re: [HACKERS] Online backup cause boot failure, anyone know why? "Richard" <husttripper(a)vip.sina.com> writes: > For perfromance purpose , I change the pg_start_backup checkpoint type from CHECKPOINT_WAIT to CHECKPOINT_IMMEDIATE, does it matter? Oh, so this isn't so much "8.3.7" as "randomly-hacked-up 8.3.7". Yes, that'd break it, I believe. CHECKPOINT_IMMEDIATE doesn't imply waiting. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Richard" on 5 Aug 2010 09:20 PS : I am using PG 8.3.7 ------------------ Richard 2010-08-05 ------------------------------------------------------------- �����ˣ�Richard �������ڣ�2010-08-05 21:19:27 �ռ��ˣ�pgsql-hackers ���ͣ� ���⣺Online backup cause boot failure, anyone know why? 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! -------------- Richard 2010-08-05 -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Robert Haas on 5 Aug 2010 10:07 On Thu, Aug 5, 2010 at 9:50 AM, Richard <husttripper(a)vip.sina.com> wrote: > 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? The transaction logs archived during the backup? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 5 Aug 2010 10:44
"Richard" <husttripper(a)vip.sina.com> writes: > For perfromance purpose , I change the pg_start_backup checkpoint type from CHECKPOINT_WAIT to CHECKPOINT_IMMEDIATE, does it matter? Oh, so this isn't so much "8.3.7" as "randomly-hacked-up 8.3.7". Yes, that'd break it, I believe. CHECKPOINT_IMMEDIATE doesn't imply waiting. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |