Conversation

Notices

1. Embed this notice
   John-Mark Gurney (encthenet@flyovercountry.social)'s status on Tuesday, 18-Feb-2025 05:44:50 JST John-Mark Gurney

   Congratulations to all the idiot dbs who violate the SQL standard in the name of better benchmarks because some db decided to do this so everyone else had to follow suite.

   https://www.postgresql.org/docs/current/sql-set-transaction.html

   > SERIALIZABLE is the default transaction isolation level in the standard. In PostgreSQL the default is ordinarily READ COMMITTED, but you can change it as mentioned above.

   > https://fosstodon.org/users/bert_hubert/statuses/114015452562488619

   • Embed this notice
     feld (feld@friedcheese.us)'s status on Tuesday, 18-Feb-2025 05:44:48 JST feld

     in reply to
     @encthenet SERIALIZABLE is what you should want for safety, right? Because it can detect if there's an issue and you need to resubmit the transaction?
     
     And nearly everyone's abandoned that by default for performance?
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Tuesday, 18-Feb-2025 08:16:57 JST feld

     in reply to
     @encthenet I'm a little surprised Postgres isn't using SERIALIZABLE by default
   • Embed this notice
     John-Mark Gurney (encthenet@flyovercountry.social)'s status on Tuesday, 18-Feb-2025 08:16:58 JST John-Mark Gurney

     in reply to

     • feld

     @feld
     Correct. It's by default the safest.

     But you can use other modes and should if you know certain guarantees about your query/data. Most people are too lazy or don't spend the time to learn what is needed to go fast.

   • Embed this notice
     feld (feld@friedcheese.us)'s status on Tuesday, 18-Feb-2025 08:29:05 JST feld

     in reply to
     @encthenet I still trust Postgres though. I have never lost data with it. MySQL on the other hand.... :sweatdrop:
     
     Same reason I keep using FreeBSD. I just trust the devs more.
   • Embed this notice
     John-Mark Gurney (encthenet@flyovercountry.social)'s status on Tuesday, 18-Feb-2025 08:29:06 JST John-Mark Gurney

     in reply to

     • feld

     @feld
     I'm not. When the other dbs default to unsafe and safe makes your DB a magnitude slower, you look slow and rarely do people test/understand safety. So they have to be unsafe like everyone else.

     See Linux w/ unsafe async writes making FreeBSD look "slow".