Summary
The release notes should have an explicit statement on the fact that up to 18.6 the server binary was shipped with debug_assertions enabled
https://edb.slack.com/archives/C01CK2TSPG9/p1787227341882759?thread_ts=1787222913.475799&cid=C01CK2TSPG9
so, as this case shows, https://techsupport.enterprisedb.com/tickets/64743 , a corruption case would have caused a sigabrt .
I think this sould be highlighted
Where did you see the problem?
https://github.com/EnterpriseDB/docs/blob/6c1b450e0a329ebbe810347bc0b997f359a6cba3/product_docs/docs/pge/18/release_notes/rel_notes18.3.0.mdx
Expected behavior
No response
Screenshots
No response
Browser / Platform
No response
Additional notes
No response
Summary
The release notes should have an explicit statement on the fact that up to 18.6 the server binary was shipped with debug_assertions enabled
https://edb.slack.com/archives/C01CK2TSPG9/p1787227341882759?thread_ts=1787222913.475799&cid=C01CK2TSPG9
so, as this case shows, https://techsupport.enterprisedb.com/tickets/64743 , a corruption case would have caused a sigabrt .
I think this sould be highlighted
Where did you see the problem?
https://github.com/EnterpriseDB/docs/blob/6c1b450e0a329ebbe810347bc0b997f359a6cba3/product_docs/docs/pge/18/release_notes/rel_notes18.3.0.mdx
Expected behavior
No response
Screenshots
No response
Browser / Platform
No response
Additional notes
No response