[–] 9 points 7 months ago (4 children)

Getting back from holiday in a few hours and the weather is cold? Turn the heating on from your app before you get back. Wow. Life changing. Don't have a use case for most things being connected but thermostat really isn't that crazy IMO.

  • source
  • parent
  • context
  • [+] -6 points 7 months ago (5 children)

    If my dentist is a racist, should I not go to the dentist? Seems like letting my oral hygiene suffer because of it would be a case of cutting off my nose to spite my face. In your search for a life lived in ideologically purity have you found some acceptable alternative?

  • source
  • parent
  • context
  • [–] -3 points 7 months ago*

    It's weird though. One of the accounts I tagged has just become more and more reasonable and I feel like. Idk. They certainly weren't all bad or deceptive people -- and being mean to and about them won't really help them figure it out ... OTOH fuck ppl who do stupid shit because they're too proud to accept inherent complicity in the evils of the lesser.

  • source
  • parent
  • context
  • [–] 1 point 7 months ago* (5 children)

    Lol what an absurd take. A transaction is a sequence of operations, not a single one, so even small tables can meet that threshold with enough query logic. I guess you're unfamiliar with medium to large datasets, but it's not uncommon to use the aggregate functions that SQL provides in real world situations, and on large tables that can easily reasonably exceed 1s. Toy my arse. Go play with yourself

    Although this is no surprise tbh because apparently you don't understand why transactions are even necessary. Benchmarks shmenchmarks. Whether it works is more important.

    I do not apologise for the downvote because this is smug shit only a junior would say

  • source
  • parent
  • context
  • [–] 1 point 8 months ago (7 children)

    But adding it to an 80ms operation is. If your operation is 0.5ms it's either a read on a small table, or maybe a single write -- transaction isolation wouldn't even be relevant there. You're right that I did mean consistency rather that integrity though, slip of the terminology, but not really worth quibbling over. The point I meant was that I like my data to make sense, a funny quirk of mine.

  • source
  • parent
  • context
  • [–] 1 point 8 months ago* (9 children)

    Well it depends how much data integrity is worth to you, and how your system works. Every write in postgres is already a transaction - when you can get away with simple crud stuff, often there's nothing to do, you have transactionality already. Transaction isolation levels are where db operation costs might change under concurrent conflicting writes but you can tune that by ensuring single-writer-per-partition or whatever in your server logic and it might add a ms or two. OTOH if you have heavy contestation it can be much more expensive. The performance implications are complicated but can certainly kept to a fraction of overall cost depending on your workload!

  • source
  • parent
  • context
  • view more: ‹ prev next ›