> but I'm curious as to what are the problems of storing them in db.
Re-checking as a result of this conversation did remind me that one pretty much ends-up with a necessary garbage collection daemon or timer, because most of the databases *don't* expose a callback for destructors on failed transactions (SQLite included).
This can result in considerable wasted resources (borg compaction being a manual step has similar drawbacks; its handling failed/orphaned objects is frequently considerably worse).
SQLite has size limits for blobs that are set at compile-time, by default 1GB.
PostgreSQL has similar limits for inline blobs, while its Large Object facility has single-table storage limits that shouldn't apply because it should be using automatically-generated partitioned tables for the feature.
The others are a mix of the same and having a bunch of issues *as DBMSes* that make them a bad choice in general.
> This is what pragma synchronous is about
Ah, the interaction I had missed. Combined with the previous pragmas you mentioned, one *could* have something reasonable with that.
LisPi
npub132…qgzqx
2026-10-07 05:44:31 UTC
in reply to nevent1q…0xtm
Author Public Key
npub1326y4p8mw4l750yc8e52n0xguvcl5j0dn88ul5r2gjva2sh2ay7qjqgzqxSeen on
wss://relay.momostr.pinkPublished at
2026-10-07 05:44:31 UTCEvent JSON
{
"id": "81cd8fce04c7fe7176fed2ec6bf7aa3ee5586aaa1ef246b2d3c4a736dec4b9f1",
"pubkey": "8ab44a84fb757fea3c983e68a9bcc8e331fa49ed99cfcfd06a4499d542eae93c",
"created_at": 1791351871,
"kind": 1,
"tags": [
[
"p",
"9096c95c05b71521d6812b521bc02db89f6677a33ce3670d9af2bcfee5042497"
],
[
"e",
"3acaeda9aba45f18c5f17442b5187574dcf07ad2bb0c7810caf2f9aeee471550",
"",
"root",
"8ab44a84fb757fea3c983e68a9bcc8e331fa49ed99cfcfd06a4499d542eae93c"
],
[
"p",
"8ab44a84fb757fea3c983e68a9bcc8e331fa49ed99cfcfd06a4499d542eae93c"
],
[
"e",
"0d2e3ef028eeae441d184818016714076dbb61ad5f9c279467f623ae560d63de",
"",
"reply",
"256c71390808dd435898b3cff116683ab924d6387efea5206c4d35b1f49551b6"
],
[
"p",
"256c71390808dd435898b3cff116683ab924d6387efea5206c4d35b1f49551b6"
],
[
"proxy",
"https://udongein.xyz/objects/f11226f3-56a4-4527-87ce-6edb2b3c0396",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://udongein.xyz/objects/f11226f3-56a4-4527-87ce-6edb2b3c0396",
"pink.momostr"
],
[
"-"
]
],
"content": "\u003e but I'm curious as to what are the problems of storing them in db.\r\n\r\nRe-checking as a result of this conversation did remind me that one pretty much ends-up with a necessary garbage collection daemon or timer, because most of the databases *don't* expose a callback for destructors on failed transactions (SQLite included).\r\n\r\nThis can result in considerable wasted resources (borg compaction being a manual step has similar drawbacks; its handling failed/orphaned objects is frequently considerably worse).\r\n\r\nSQLite has size limits for blobs that are set at compile-time, by default 1GB.\r\n\r\nPostgreSQL has similar limits for inline blobs, while its Large Object facility has single-table storage limits that shouldn't apply because it should be using automatically-generated partitioned tables for the feature.\r\n\r\nThe others are a mix of the same and having a bunch of issues *as DBMSes* that make them a bad choice in general.\r\n\r\n\u003e This is what pragma synchronous is about\r\n\r\nAh, the interaction I had missed. Combined with the previous pragmas you mentioned, one *could* have something reasonable with that.",
"sig": "caf9ad382f76c2b4d298ad9b86a1ceba001202ef03d4e6c3b6777c3145a90e19aa64332829c71b77943bdea1bef41975b7ac038d1df38cb0db4d608d51340c4d"
}