We've relied on this property in the past, to prove to an installation that the database corruption they were experiencing wasn't an LMDB bug - it turned out to be a faulty DRAM DIMM in their server. Without LMDB's deterministic write behavior, convincing someone of these cases would be a lot more difficult.
But proving the presence of a bug and narrowing down its cause are really two different tasks, and thus requires two different types of logging.
Howard Chu @ Symas /
npub1tt4…x9ud
2023-12-24 12:55:01
in reply to nevent1q…xvhj
Author Public Key
npub1tt4j2zeswksjh5z7zmy283qd4yd920afy9j28xg45wsxzhl9rpjqrex9udPublished at
2023-12-24 12:55:01Event JSON
{
"id": "45952ed27a7d143fca96fc86fc62bab77bbb032afdc2a5902e760f6e3e852721",
"pubkey": "5aeb250b3075a12bd05e16c8a3c40da91a553fa92164a39915a3a0615fe51864",
"created_at": 1703418901,
"kind": 1,
"tags": [
[
"e",
"1520711c3045214bcc2c41dfb2858826fb089b0ac7582b7aed0d65afd34468f7",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/hyc/statuses/111635261156491245",
"activitypub"
]
],
"content": "We've relied on this property in the past, to prove to an installation that the database corruption they were experiencing wasn't an LMDB bug - it turned out to be a faulty DRAM DIMM in their server. Without LMDB's deterministic write behavior, convincing someone of these cases would be a lot more difficult.\n\nBut proving the presence of a bug and narrowing down its cause are really two different tasks, and thus requires two different types of logging.",
"sig": "eada3f9ce134662f1863362616c8a197c96ff1b83b9d4c25959824e2eed85d92b81ad5d5b283b85e5a6f21e4b8469e0f58a2536cd74bc372cb062b444e3a4611"
}