Corrupt index lead to skipped autovacuum - Mailing list pgsql-bugs
Postgres version: postgres (PostgreSQL) 16.3 (Ubuntu 16.3-1.pgdg20.04+1)
Related extension: vector | 0.6.2 | public | vector data type and ivfflat and hnsw access methods
We have a database running with vector extension and somehow one of the index is corrupted. During autovacuum the following message shows up:
different vector dimensions 256 and 0
Related extension: vector | 0.6.2 | public | vector data type and ivfflat and hnsw access methods
We have a database running with vector extension and somehow one of the index is corrupted. During autovacuum the following message shows up:
different vector dimensions 256 and 0
while vacuuming index "ai_user_embedding_idx" of relation "public.ma_ai_aiuser"
automatic vacuum of table "analytics_vector.public.ma_ai_aiuser"
The problem is that after this error, the autovacuum process seems to stop here. All other tables and indexes are left unvacuumed even if they already exceed emergency vacuum threshold. Once we reindex the index, autovacuum starts to work properly.
We will expect the autovacuum will continue to vacuum other tables/indexes and maybe mark the index as invalid? Skip vacuum for all other indexes / tables can be quite dangerous if un-noticed.
Thanks!
automatic vacuum of table "analytics_vector.public.ma_ai_aiuser"
The problem is that after this error, the autovacuum process seems to stop here. All other tables and indexes are left unvacuumed even if they already exceed emergency vacuum threshold. Once we reindex the index, autovacuum starts to work properly.
We will expect the autovacuum will continue to vacuum other tables/indexes and maybe mark the index as invalid? Skip vacuum for all other indexes / tables can be quite dangerous if un-noticed.
Thanks!
高偉鈞｜Wei-Chun Kao
技術長｜CTO
T：(02) 2521-7375｜M：0920-605-597
A：105402 台北市松山區民生東路三段109號17樓 (聯邦大廈)
17F., No. 109, Sec. 3, Minsheng E. Rd., Songshan Dist., Taipei City 105402, Taiwan (R.O.C.)
pgsql-bugs by date: