| From: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Kamigishi Rei <iijima(dot)yun(at)koumakan(dot)jp>, David Rowley <dgrowley(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17245: Index corruption involving deduplicated entries |
| Date: | 2021-10-28 21:39:50 |
| Message-ID: | CALT9ZEFr2B5yFw==1TfYZY-hC-6JvkN3MeUsZ1NkrDDuGfjQ9A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
One hypothesis just out-of-the air:
If heap page visibility map bit is wrongly set to all_visible, index-only
scan can give duplicates (in effect new and old versions of the same row),
with no apparent corruption of neither index nor heap relation. It just
skips checking visibility of tuples in heap. Not sure it's the case now,
but I've seen this previousy.
It could be diagnosed by deletion of VM file for a relation, the error (if
it is this error) will disappear.
--
Best regards,
Pavel Borisov
Postgres Professional: http://postgrespro.com <http://www.postgrespro.com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-10-28 21:42:09 | Re: BUG #17245: Index corruption involving deduplicated entries |
| Previous Message | Thomas Munro | 2021-10-28 21:39:37 | Re: BUG #17245: Index corruption involving deduplicated entries |