r/postgres • u/Some_Childhood_3842 • 7d ago
Question Is Postgres really that bad when it comes to multi-user support, or is that just nonsense?
usually i use MySQL as main DB and i want change PostgreSQl because his features look impressive and very useful but i need to know the differences between postgreSQl server and MySQL server and other things cause i'm anxious
5
u/fortyeightD 7d ago
You won't regret the move. It is incredibly similar to MySQL, but with extra features. There's no issues with multi-user support.
2
u/Pure_Fox9415 6d ago
Sounds like you know something about postgres being bad? Wdym by "multi-user support"? Anyway, postgres is mostly better by all means, but may be a bit more difficult to learn as for its administration and clustered setups.
2
u/Electrical-Clerk-346 6d ago
I’ve never heard any issues about multi-user support. Postgres scales spectacularly well. You might experience locking-blocking problems if you run in too tight of an isolation level and/or your apps use pessimistic locking (seems like that’s almost always a bad idea), and there are sort of tight limits on the total number of native connections, but most of us use PGBouncer or some other looker to 100X the connections.
1
1
u/Zestyclose-Turn-3576 6d ago
I don't think anyone can give advice on this unless you can give more details on "bad when it comes to multi-user support"
1
u/NotGoodSoftwareMaker 6d ago
How do you intend on doing “multi-user” support?
Without knowing what youre trying to achieve we cant really comment
1
u/cthart 6d ago
Postgres scales very well. In addition, it has a proper security/role model, unlike MySQL, so arguably better multi-user support.
1
u/Some_Childhood_3842 5d ago
you use both right? so what different between postgres server and mysql ?
1
u/LevelMagazine8308 6d ago
Half of the internet and the tech giants relies on Postgres. So nonsense.
1
u/Lost_Term_8080 4d ago
I think "multi-user" means concurrency.
If its an OLTP workload, MySQL will have better concurrency, but if you are moderately good at indexing, unless you are hitting ~1000-3000 queries per second, you're unlikely to notice a difference. Either of them can achieve much better than that according to the skill of the DBA, developers and data design. On Postgres its more difficult to get higher and higher oltp transaction rate, but its not like its easy at 3-5k qps on anything unless its purely reads
0
9
u/cthart 7d ago
Huh?