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

From Jan Wieck
Subject Re: transaction lost when delete clog file after normal shutdown
Date
Msg-id 5e088692-e242-4d3f-9ad0-ada8162b7c32@wi3ck.info
Whole thread Raw
In response to Re: Re: transaction lost when delete clog file after normal shutdown  ("章晨曦@易景科技" <zhangchenxi@halodbtech.com>)
Responses Re: transaction lost when delete clog file after normal shutdown
List pgsql-hackers
On 12/23/24 06:01, 章晨曦@易景科技 wrote:
> 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.

Why would you trust the other 99.999 TB if something corrupted the clog 
file?


Regards, Jan

> 
> 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: Melanie Plageman
Date:
Subject: Re: Eagerly scan all-visible pages to amortize aggressive vacuum
Next
From: Matthias van de Meent
Date:
Subject: Re: help in allocating shared module within a module