Re: Re: transaction lost when delete clog file after normal shutdown - Mailing list pgsql-hackers

From 章晨曦@易景科技
Subject Re: Re: transaction lost when delete clog file after normal shutdown
Date
Msg-id tencent_58C8C4754784AD193BBB506F@qq.com
Whole thread Raw
In response to transaction lost when delete clog file after normal shutdown  ("章晨曦@易景科技" <zhangchenxi@halodbtech.com>)
Responses Re: transaction lost when delete clog file after normal shutdown
Re: transaction lost when delete clog file after normal shutdown
List pgsql-hackers
Yes, of course we can solve this by restoring from backup. 
But if the database volumn is large, say, 100TB or more, the cost
is really too expensive just because the tiny clog file corrupt.

Regards,
Jet

Daniel Gustafsson<daniel@yesql.se> 在 2024年12月23日 周一 18:43 写道:
> On 23 Dec 2024, at 11:36, 章晨曦@易景科技 <zhangchenxi@halodbtech.com> wrote:

> Human errors, disk errors, or even cosmic rays ...

That sounds exactly like the scenario which backups are made for.  In all these
error cases there is no way of being sure that no other part of the system has
been compromised, so you restore from backup with WAL replay.

--
Daniel Gustafsson

pgsql-hackers by date:

Previous
From: Andrey Borodin
Date:
Subject: Re: transaction lost when delete clog file after normal shutdown
Next
From: Heikki Linnakangas
Date:
Subject: Re: Exporting float_to_shortest_decimal_buf(n) with Postgres 17 on Windows