Re: Re: transaction lost when delete clog file after normal shutdown

From: 章晨曦(at)易景科技 <zhangchenxi(at)halodbtech(dot)com>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: 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 10:03:38
Message-ID: tencent_0064182A1A7886832E88D318@qq.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

S1:
When database normal shutdown, and clog file missing, the database cannot restart. And if make a zero clog file, database started but may cause transactions lost.

S2:
When database crashed, and&nbsp;&nbsp;clog file missing, when database restart, it will try to recover. And everything is ok

So I think we may improve the database more reliable in some scenarios, e.g. Only&nbsp;clog file corrupted or missing, like S1

Regards,
Jet

Andrey Borodin<x4mmm(at)yandex-team(dot)ru&gt;&nbsp;在 2024年12月23日 周一 17:51 写道:

&gt; On 23 Dec 2024, at 14:12, 章晨曦(at)易景科技 <zhangchenxi(at)halodbtech(dot)com&gt; wrote:
&gt;
&gt; we simulate crash and clog file corrupt (delete the clog file)

Clog file cannot disappear as a result of a crash. What makes you think otherwise?

Best regards, Andrey Borodin.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniil Davydov 2024-12-23 10:11:59 Re: Repeatable read transaction doesn't see dropped table
Previous Message Heikki Linnakangas 2024-12-23 10:01:26 Re: Repeatable read transaction doesn't see dropped table