Make multixact error message more explicit
Alvaro Herrera <alvherre@alvh.no-ip.org>
Make multixact error message more explicit There are recent reports involving a very old error message that we have no history of hitting -- perhaps a recently introduced bug. Improve the error message in an attempt to improve our chances of investigating the bug. Per reports from Dimos Stamatakis and Bob Krier. Backpatch to 11. Discussion: https://postgr.es/m/CO2PR0801MB2310579F65529380A4E5EDC0E20A9@CO2PR0801MB2310.namprd08.prod.outlook.com Discussion: https://postgr.es/m/17518-04e368df5ad7f2ee@postgresql.org
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/access/transam/multixact.c | modified | +2 −1 |
Discussion
- Fix for visibility check on 14.5 fails on tpcc with high concurrency 12 messages · 2022-11-22 → 2023-04-26
- BUG #17518: Getting Error "new multixact has more than one updating member" when trying to delete records. 6 messages · 2022-06-14 → 2022-06-28