Re: FailedAssertion in heap_index_delete_tuples at heapam.c:7220
От | Peter Geoghegan |
---|---|
Тема | Re: FailedAssertion in heap_index_delete_tuples at heapam.c:7220 |
Дата | |
Msg-id | CAH2-Wz=rCyFs3vQO57zD8AOeyH6yo0fgtmiCdo0RDNeJQbVs6Q@mail.gmail.com обсуждение исходный текст |
Ответ на | FailedAssertion in heap_index_delete_tuples at heapam.c:7220 (Jaime Casanova <jcasanov@systemguards.com.ec>) |
Ответы |
Re: FailedAssertion in heap_index_delete_tuples at heapam.c:7220
|
Список | pgsql-hackers |
On Tue, Jan 26, 2021 at 10:52 PM Jaime Casanova <jcasanov@systemguards.com.ec> wrote: > ${subject} happened while executing ${attached query} at regresssion > database, using 14dev (commit > d5a83d79c9f9b660a6a5a77afafe146d3c8c6f46) and produced ${attached > stack trace}. I see the bug: gistprunepage() calls index_compute_xid_horizon_for_tuples() (which ultimately calls the heapam.c callback for heap_index_delete_tuples()) with an empty array, which we don't expect. The similar code within _hash_vacuum_one_page() already only calls index_compute_xid_horizon_for_tuples() when ndeletable > 0. The fix is obvious: Bring gistprunepage() in line with _hash_vacuum_one_page(). I'll go push a fix for that now. Thanks for the report! -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: