Re: The ability of postgres to determine loss of files of the main fork

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, Michael Banck <mbanck(at)gmx(dot)net>
Cc: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Frits Hoogland <frits(dot)hoogland(at)gmail(dot)com>
Subject: Re: The ability of postgres to determine loss of files of the main fork
Date: 2025-10-06 12:07:47
Message-ID: 946a9fd4468f8d72aa7629a51a6349caf35e8a50.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2025-10-06 at 11:19 +0200, Jakub Wartak wrote:
> Anyway, I do not know if opening all the files on startup (or just
> crash-recovery?) is the proper way

I am not sure if you understand the problem at hand: how can you
tell that a segment of a relation is missing? You have to know that
there should be a file before you can try to open it.

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2025-10-06 12:51:07 src/include/utils/float.h comment one link stable
Previous Message Ranier Vilela 2025-10-06 12:06:08 Re: Fix misuse use of window_gettupleslot function (src/backend/executor/nodeWindowAgg.c)