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

From: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, Michael Banck <mbanck(at)gmx(dot)net>, 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-01 11:45:59
Message-ID: CAJ7c6TMCyhX4Z7FrS=ORCcKS1F_iZzfUuQM3shx64WKynoxjsA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Jakub,

> IMHO all files should be opened at least on startup to check integrity,

That might be a lot of files to open. Even if you can open a file it
doesn't mean it's not empty or is not corrupted.

--
Best regards,
Aleksander Alekseev

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-10-01 11:55:55 Re: Add jsonb_translate(jsonb, from, to)
Previous Message Jakub Wartak 2025-10-01 11:20:48 Re: The ability of postgres to determine loss of files of the main fork