No. I meant a developer. I did not mean SREs and DBAs, as those typically need to know far too much of the innards of the systems they are maintaining. But a

No. I meant a developer. I did not mean SREs and DBAs, as those typically need to know far too much of the innards of the systems they are maintaining. But a developer? I honestly don't really care that "(BIG) TEXT" is stored using something called TOAST[1] in postgres. All I care about, is that I can store large texts of varying lengths. The original argument, to me, sounded very much like someone with a lot of knowledge coming in and explaining "no, VARCHAR and TEXT are very different!". Sure, for someone hacking away on the storage-engine or even someone tuning pg, they are. But for "the average developer"? They are the same. Sure, I am aware that all abstractions are leaky. But e.g. TEXT in pg is a good example, because I really didn't have to care, it just worked the same as storing ints, strings, etc. Untill it didn't and I had to go down that rabbithole, hence why I do know about it, as software dev - as user of postgres. And about URIs: I didn't mean you'd get a data:uri. I didn't even imply that. I really meant a URI to where the asset can be found online: some S3 URI or so. [1] https://blog.rustprooflabs.com/2020/07/postgres-storing-large-text https://blog.rustprooflabs.com/2020/07/postgres-storing-larg...