1127

I'll see myself out (media.piefed.social)

submitted 1 day ago by Ek-Hou-Van-Braai@piefed.social to c/programmer_humor@programming.dev

51 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] lmr0x61@lemmy.ml 88 points 1 day ago

As mentioned elsewhere, this is appropriate for anyone doing database administration, because DB writes should always be a trans action.

[-] Tja@programming.dev 4 points 15 hours ago

I get that this is a joke, but....

... ackshually it should almost never be a transaction only when there's absolutely no other option, because transactions kill your performance.

[-] silasmariner@programming.dev 3 points 8 hours ago

Actually transactions can be a secomd-layer safety-net for single-responsibility writers to ensure rollback on eg restarts and consistency on loadbalancer redecisions without having much of an impact on performance, and data integrity is usually quite important.

[-] Tja@programming.dev 1 points 1 hour ago

As long as the database is acid restarts should not be a factor. Data integrity is not helped by transactions, you would need error correcting codes for that. Plus the effect on performance is quite notable on all dbs I've worked with.

[-] silasmariner@programming.dev 1 points 1 hour ago

Restarts in a server between dB updates that in a sane world would be txns I meant (e.g update A, crash so don't update B). Anyway, in postgres they're pretty cheap in the absence of actual conflict -- more expensive if you have actual cinflicts, obvs.