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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Frits Hoogland <frits(dot)hoogland(at)gmail(dot)com>, Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: The ability of postgres to determine loss of files of the main fork
Date: 2025-10-01 13:49:10
Message-ID: cbnna46p73gtyzbw22x67vuihcqmqwfbjgbzkdmrynovatvjlf@kwks4cei2jgh
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2025-10-01 15:39:04 +0200, Laurenz Albe wrote:
> On Wed, 2025-10-01 at 13:58 +0200, Frits Hoogland wrote:
> > I am proposing the database to have the ability to detect when it has missing segments.
>
> Just a random idea: one solution would be if each segment has a flag that indicates
> if that is the last segment or not. But that would break the on-disk storage format,
> unless there is room left for an extra flag somewhere in the current layout.

It'd also make extensions / truncations more complicated. I rather doubt we're
going there. Right now relation extension aren't WAL logged. While there might
be reasons to change that, I don't think this is enough justification for
doing so.

Greetings,

Andres

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2025-10-01 14:21:22 Re: [BUG]: the walsender does not update its IO statistics until it exits
Previous Message Laurenz Albe 2025-10-01 13:39:04 Re: The ability of postgres to determine loss of files of the main fork