Hello!
> Originally I investigated the customer's problem with PG16. And have
> reproduced it for pg16,. I checked that relevant amcheck code was not
> changed since pg16, so I thought that the problem takes place for all
> Postgres versions. But looks like it is not true.
I think it is still broken, but with less probability.
Have you tried injection points on v16? Such a test case will make
things much more clear.
Also, I added Alexander to CC (he is author of bt_child_highkey_check)
- maybe the issue is easily understandable for him.
Best regards,
Mikhail.
