| From: | 章晨曦(at)易景科技 <zhangchenxi(at)halodbtech(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Junwang Zhao <zhjwpku(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Re: transaction lost when delete clog file after normal shutdown |
| Date: | 2024-12-23 11:01:01 |
| Message-ID: | tencent_58C8C4754784AD193BBB506F@qq.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)yesql(dot)se> 在 2024年12月23日 周一 18:43 写道：
> On 23 Dec 2024, at 11:36, 章晨曦(at)易景科技 <zhangchenxi(at)halodbtech(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2024-12-23 11:05:27 | Re: Exporting float_to_shortest_decimal_buf(n) with Postgres 17 on Windows |
| Previous Message | Andrey Borodin | 2024-12-23 10:52:50 | Re: transaction lost when delete clog file after normal shutdown |