Re: transaction lost when delete clog file after normal shutdown

From: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
To: Jan Wieck <jan(at)wi3ck(dot)info>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: transaction lost when delete clog file after normal shutdown
Date: 2024-12-24 01:45:49
Message-ID: CAGjGUAKBxYWgXyhWBxe0WMuieoNoMYCPan-qnYcJF4J456Xdcw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

On Tue, 24 Dec 2024 at 02:06, Jan Wieck <jan(at)wi3ck(dot)info> wrote:

> On 12/23/24 06:01, 章晨曦(at)易景科技 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(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
> >
>
>
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrei Lepikhov 2024-12-24 01:49:02 Re: Add Postgres module info
Previous Message David E. Wheeler 2024-12-23 22:26:08 Re: Add Postgres module info