Reality would prove to be different.
In Mongo, when using w: 1 in a write concern, the write operation is acknowledged after being successfully applied to the primary's instance memory. However, w: 1 alone does not guarantee durability unless combined with j: true (journaling). Running standalone Mongo, as we did in the tests, defaults to j: false. I have explicitly set it to true in the testing script to make write comparisons to Postgres objective. You can dive deeper into this here: https://www.mongodb.com/docs/manual/reference/write-concern/#acknowledgment-behavior and here: https://www.mongodb.com/docs/manual/core/journaling/. Unfortunately, docs are a bit convoluted about it，推荐阅读体育直播获取更多信息
h->next = to_be_deleted[classno];，更多细节参见Line官方版本下载
（三）对本章规定的举证责任作出相反的约定；