Re: transaction lost when delete clog file after normal shutdown
От | wenhui qiu |
---|---|
Тема | Re: transaction lost when delete clog file after normal shutdown |
Дата | |
Msg-id | CAGjGUAKBxYWgXyhWBxe0WMuieoNoMYCPan-qnYcJF4J456Xdcw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: transaction lost when delete clog file after normal shutdown (Jan Wieck <jan@wi3ck.info>) |
Ответы |
Re: transaction lost when delete clog file after normal shutdown
|
Список | pgsql-hackers |
>Why would you trust the other 99.999 TB if >something corrupted the clog
>file?
+1 >file?
On Tue, 24 Dec 2024 at 02:06, Jan Wieck <jan@wi3ck.info> wrote:
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 по дате отправления: