| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | nbtree's ScalarArrayOp array mark/restore code appears to be buggy |
| Date: | 2023-09-23 03:17:16 |
| Message-ID: | CAH2-WzkgP3DDRJxw6DgjCxo-cu-DKrvjEv_ArkP2ctBJatDCYg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Attached test case demonstrates an issue with nbtree's mark/restore
code. All supported versions are affected.
My suspicion is that bugfix commit 70bc5833 missed some subtlety
around what we need to do to make sure that the array keys stay "in
sync" with the scan. I'll have time to debug the problem some more
tomorrow.
My ScalarArrayOp project [1] seems unaffected by the bug, so I don't
expect it'll take long to get to the bottom of this. This is probably
due to its general design, and not any specific detail. The patch
makes the relationship between the current scan position and the
current array keys a great deal looser.
[1] https://commitfest.postgresql.org/44/4455/
--
Peter Geoghegan
| Attachment | Content-Type | Size |
|---|---|---|
| nbtree_array_mark_restore_bug.sql | application/octet-stream | 2.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2023-09-23 04:48:19 | RE: [PoC] pg_upgrade: allow to upgrade publisher node |
| Previous Message | Jeff Davis | 2023-09-23 01:57:19 | Re: Questions about the new subscription parameter: password_required |