Re: The ability of postgres to determine loss of files of the main fork
От | Laurenz Albe |
---|---|
Тема | Re: The ability of postgres to determine loss of files of the main fork |
Дата | |
Msg-id | 45b3a1dd6be28dd409850a5503c029a97ca0754e.camel@cybertec.at обсуждение исходный текст |
Ответ на | Re: The ability of postgres to determine loss of files of the main fork (Aleksander Alekseev <aleksander@tigerdata.com>) |
Ответы |
Re: The ability of postgres to determine loss of files of the main fork
|
Список | 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 по дате отправления: