| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, Frits Hoogland <frits(dot)hoogland(at)gmail(dot)com> |
| Cc: | 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 06:26:50 |
| Message-ID: | 45b3a1dd6be28dd409850a5503c029a97ca0754e.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-10-01 06:39:35 | Re: Remove custom redundant full page write description from GIN |
| Previous Message | jian he | 2025-10-01 06:16:42 | Re: Emitting JSON to file using COPY TO |