From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | bharath(dot)rupireddyforpostgres(at)gmail(dot)com, nathandbossart(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: thinko in basic_archive.c |
Date: | 2022-10-19 14:48:03 |
Message-ID: | CA+TgmoY_4A7RPQRg0Qaq0GqB79FvSqnoS49RZdTk3pjj64MgZw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 18, 2022 at 11:28 PM Kyotaro Horiguchi
<horikyota(dot)ntt(at)gmail(dot)com> wrote:
> > > Yeah, leaving a potentially unbounded number of files around after
> > > system crashes seems pretty unfriendly. I'm not sure how to fix that,
> > > exactly.
>
> Unbounded number of sequential crash-restarts itself is a more serious
> problem..
They don't have to be sequential. Garbage could accumulate over weeks,
months, or years.
Anyway, I agree we should hope that the system doesn't crash often,
but we cannot prevent the system administrator from removing the power
whenever they like. We can however try to reduce the number of
database-related things that go wrong if this happens, and I think we
should. Bharath's patch seems like it's probably a good idea, and if
we can do better, we should.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Melih Mutlu | 2022-10-19 14:59:22 | Re: Mingw task for Cirrus CI |
Previous Message | Robert Haas | 2022-10-19 14:40:21 | Re: Avoid memory leaks during base backups |