News for hackers. Stuff that matters.
Re:Oracle lays off more than 200 California-based workers by AmericanChopper on Saturday October 15, 2022 @12:50AM (#33211851)
You need to have database expertise if you want to operate a database at any significant scale. All of those configuration parameters don’t go away just because you’re not asked by the software to configure them. There are a lot of use cases out there where a more simple product would be most suitable, but I’ve seen plenty of instances of choosing a more simple tool and then one by one encountering every single problem that a more sophisticated RDBMs would be capable of easily solving.

Also, I really like Postgres, but it’s a nightmare to work with at scale. Even simply things like execution plan monitoring and management are tedious in Postgres, but incredibly easy to stay on top of with the _tooling_ provided by Oracle.

Re:Oracle lays off more than 200 California-based workers by fuy on Saturday October 15, 2022 @03:52AM (#33212744)
Having migrated large codebase/product from SQL Server to Postgres, can definitely relate. I love Postgres as a developer, but from DBA/devops perspective, Postgres requires babysitting where SQL Server just works. Things like having to manually customize work_mem for complex queries feels very cumbersome and is very inefficient, - it should be solved by software.