[dead]
Ways to shoot yourself in the foot with Postgres
291–300 of 329 posts
Re: Ways to shoot yourself in the foot with Postgres
#292[dead]
Re: Ways to shoot yourself in the foot with Postgres
#293[dead]
Re: Ways to shoot yourself in the foot with Postgres
#294[dead]
Re: Ways to shoot yourself in the foot with Postgres
#295[dead]
Re: Ways to shoot yourself in the foot with Postgres
#296[dead]
Re: Ways to shoot yourself in the foot with Postgres
#297The two biggest ones imo were not mentioned: 1. Contrary to popular belief, Postgres isn't fully ACID (specifically the "I") with the default isolation mode. For example, selecting the sum of a column then inserting conditionally on that creates a race condition. Serializable mode is fully isolated, but it has many caveats and shouldn't be used often, so you should instead become familiar with what's isolated and wha…
> it has many caveats and shouldn't be used often I’d argue it isn’t used enough given its isolation advantages
Serializable mode is only useful in low throughput cases. You take a big performance hit and can easily have a bunch of queries waiting one each other until the queue fills up. I haven't used it in forever, I just make sure my stuff works with the default isolation mode. You also can't slap it on like a band-aid for unsure users. The DB client has to implement retry logic, which most Postgres libs don't seem to have, and the code has to careful not to cause side effects inside the retriable area.
Spanner and some other DBMSs are fully serializable always. They do a better job of that than Postgres, I guess cause they focus on it, but they're still a lot slower in the end.
What would be cool is some extension to watch your non-serializable transactions for concurrency anomalies like 1% of the time and use that tiny sample to alert you of race conditions. Like a thread sanitizer does for code. Does that exist??
Re: Ways to shoot yourself in the foot with Postgres
#298[dead]
Re: Ways to shoot yourself in the foot with Postgres
#299[dead]
Re: Ways to shoot yourself in the foot with Postgres
#300[dead]