Re:The Great Migration from MongoDB to PostgreSQL
by simonw on Friday March 29, 2024 @09:18AM
(#39863757)
What's top of the list technically?
[ Parent
| on HN ]
Re:The Great Migration from MongoDB to PostgreSQL
by bradleyjg on Friday March 29, 2024 @09:26AM
(#39863849)
Oracle
Re:The Great Migration from MongoDB to PostgreSQL
by pmarreck on Friday March 29, 2024 @10:09AM
(#39864312)
Oracle is a giant mess, is the sense I got from trying to work with it in the past.
While I am loathe to recommend any Microsoft product, SQL Server is at least coherent, and has actual transactions like Oracle (and not just "checkpoints")
Re:The Great Migration from MongoDB to PostgreSQL
by paulryanrogers on Friday March 29, 2024 @10:29AM
(#39864527)
Aren't MSSQL and Oracle just doing redo logs, like MySQL?
What do you consider not actual transactions?
Postgresql keeps dead tuples in place until vacuumed, which seems optimized for rollbacks. But isn't so bad if you're inserting much more than deleting or updating.
Re:The Great Migration from MongoDB to PostgreSQL
by pmarreck on Saturday March 30, 2024 @08:55AM
(#39874397)
Nestable transactions = “real transactions” to me, I guess.
I almost don’t see the point in non-nestable transactions
Re:The Great Migration from MongoDB to PostgreSQL
by paulryanrogers on Saturday March 30, 2024 @09:44AM
(#39874809)
SQL standardizes SAVEPOINT for such nesting. Is that not sufficient? FWIW Postgres supports it.