Re: The ability of postgres to determine loss of files of the main fork - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: The ability of postgres to determine loss of files of the main fork
Date
Msg-id 45b3a1dd6be28dd409850a5503c029a97ca0754e.camel@cybertec.at
Whole thread Raw
In response to Re: The ability of postgres to determine loss of files of the main fork  (Aleksander Alekseev <aleksander@tigerdata.com>)
Responses Re: The ability of postgres to determine loss of files of the main fork
List pgsql-hackers
On Tue, 2025-09-30 at 18:55 +0300, Aleksander Alekseev wrote:
> > Therefore, I would like to request an enhancement: add an option to
> > verify_heapam() that causes the primary key index to be scanned and makes
> > sure that all line pointers in the index point to existing tuples.
>
> I'm a bit puzzled by your emphasis on primary keys. In Postgres it is
> legal to have tables without PKs, indexes, or even columns:
>
> =# create table my_table();
> =# select * from my_table;
>
> To clarify, are you proposing not to check such tables?

If there is no index on a table, there is no way to determine a missing
segment.  I don't think that Frits deliberately wants to *not* check
such tables, it's just that there is no way to do it as things are now.

Just because a check is not possible in certain cases is no good reason
to forgo a check in those cases where it is possible.

Yours,
Laurenz Albe



pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: Emitting JSON to file using COPY TO
Next
From: Michael Paquier
Date:
Subject: Re: Remove custom redundant full page write description from GIN