From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Fujii Masao *EXTERN*" <masao(dot)fujii(at)gmail(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: backup_label in a crash recovery |
Date: | 2009-11-02 10:05:47 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C203937FF1@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fujii Masao wrote:
> When a crash occurs before calling pg_stop_backup(),
> the subsequent crash recovery causes the FATAL error
> and outputs the following HINT message.
>
> If you are not restoring from a backup, try removing the file
> \"%s/backup_label\"."
>
> I wonder why backup_label isn't automatically removed
> in normal crash recovery case. Is this for the fail-safe
> protection; prevent admin from restoring from a backup
> wrongly without creating recovery.conf? Or another?
>
> If that's intentional, a clusterware for shared disk
> failover system should remove backup_label whenever
> doing failover. Otherwise, when a crash occurs during
> online-backup, the failover would fail.
I do not know if there is a good reason why the server does
not ignore backup_label if recovery.conf is not present.
But as it is, any failover system should definitely remove
backup_label.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2009-11-02 10:06:28 | Architecture of walreceiver (Streaming Replication) |
Postg사설 토토SQL : 사설 | Bernard Grosperrin | 2009-11-02 09:37:57 | Postg사설 토토SQL : 사설 토토 : Windows의 컴파일 |