Event JSON
{
"id": "728249c7e330eafd08ad1d94fcf4ec9bcda4b945b0cbe2933f956c0017fa926a",
"pubkey": "c5051b46c190db7d9b462748b2e3b76ebff27ee2284632fdcd413738af11e65c",
"created_at": 1685651277,
"kind": 1,
"tags": [
[
"p",
"24f36fa5142362eed31d17692a3309c81485f9da7d73cb3d768165dc8f38cc90",
"wss://relay.mostr.pub"
],
[
"p",
"0c09c8a87935511b9c4c98209a4b1cf920ff4c1e4439c6334ede6b278fc0697f",
"wss://relay.mostr.pub"
],
[
"p",
"ba52c364fdac34a202e517214e8d67a0cecb9a32d0232a9ad7e8d055e3a8526b",
"wss://relay.mostr.pub"
],
[
"p",
"85b33277eb71c9377a7d20cc4e7ea68505afdb7796c63b2bc1f12ca344c6c60e",
"wss://relay.mostr.pub"
],
[
"p",
"13ea8ad738f80e5524e29f8cc71e3820938dba3d074cc3ab3afdc2eb27a40f5d",
"wss://relay.mostr.pub"
],
[
"p",
"5a2c65dc2ab8a1ef0a47ffa051b0c6ee6c943d8239ec9d16d49b12947035811e",
"wss://relay.mostr.pub"
],
[
"e",
"1affc94e1ca15fe56e4fbd51da8f085fe56e5b75f07523c3af6405d143b219e6",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"database"
],
[
"t",
"rdbms"
],
[
"mostr",
"https://social.linux.pizza/users/mkj/statuses/110470842121626946"
]
],
"content": "nostr:npub1yneklfg5yd3wa5caza5j5vcfeq2gt7w604euk0tks9jaerecejgqrmeeut nostr:npub1psyu32rex4g3h8zvnqsf5jculys07nq7gsuuvv6wme4j0r7qd9lsh3pasy nostr:npub1hffvxe8a4s62yqh9zus5art85r8vhx3j6q3j4xkharg9tcag2f4sl7zptn Normally, a database engine should be able to lock fairly small chunks of storage to delete individual rows in a table. My guess would be that since such a cleanup presumably touches a rather large fraction of the rows in the table, the #database #RDBMS engine at some point, rather than locking individual chunks, just throws its hands in the air with a \"I'm through with this piecemeal stuff, I'll just lock the whole thing instead so I can get this over with\".",
"sig": "545e7c935064684ff773bcc5fb188af7ab52f82d4c8e7aafbe6e8ddfaac1dc84543de65863a17602cdb47139468dc7fef23fba78ab490ba0642778f011368cc8"
}