Re:PostgreSQL reconsiders its process-based model
by narrator on Monday June 19, 2023 @01:03PM
(#36393508)
The correctness problem should be handled by a suite of automated tests which PostgreSQL has. If all tests pass, the application must work correctly. The project is too big, and has too many developers to make much progress without full test coverage. Where else would up-to-date documentation regarding the correct behavior of PostgreSQL exist? In some developers head? SQLite is pretty famous for there extreme approach to testing including out of memory conditions, and other rare circumstances: https://www.sqlite.org/testing.html
[ Parent
| on HN ]
Re:PostgreSQL reconsiders its process-based model
by lukeschlather on Monday June 19, 2023 @01:15PM
(#36393714)
Parallelism is often incredibly hard to write automated tests for, and this will most likely create parallelism issues that were not dreamed of by the authors of the test suite.
Re:PostgreSQL reconsiders its process-based model
by abalashov on Monday June 19, 2023 @05:02PM
(#36396426)
> If all tests pass, the application must work correctly.
These are "famous last words" in many contexts, but when talking about difficult-to-reproduce parallelism issues, I just don't think it's a particularly applicable viewpoint at all. No disrespect. :)