News for hackers. Stuff that matters.
Re:Oracle vs. PostgreSQL – A Comment by OrangeUnicorn12 on Sunday May 31, 2020 @05:07AM (#23368259)
Some points for you, if I may:

- Why are you worried about license fees as a developer? :-) Seriously speaking, start with Oracle SE2. It is so cheap, I would use it everywhere. And if you need those "partitioning", "parallel execution" etc - your business is Enterprise, and you can afford such price tags. (I know, there will be a sh1tst0rm now, but please think about what IO said from business POV)

- Oracle Public Cloud gives you database extremely fast - and you will never have issues with license audit

- The name of "Rollback of DDLs" is "no developer access to production" and "UAT" :-)

- hmmm... $> rman rman> connect target rman> backup database plus archivelog delete input; rman> exit

What can be easier?

Are you a huge fan of Vacuuming, XID Freezing, WAL optimisations etc. etc.?

The MVCC in Postgress, in my view (!) is joke from academia, where they had not a single DBA :-)

Re:Oracle vs. PostgreSQL – A Comment by davidhalter on Sunday May 31, 2020 @05:46AM (#23368389)
Why is MVCC in Postgres a joke in academia?
[dead]
Re:Oracle vs. PostgreSQL – A Comment by GordonS on Sunday May 31, 2020 @10:37AM (#23369843)
I guess the negative reactions are because you're making statements without anything to back them up.

> Why are you worried about license fees as a developer?

Lots of developers are involved to some extent in financial decisions. And in any case, I'd be worried about losing my job because Oracle had bankrupted my employer..

> Seriously speaking, start with Oracle SE2. It is so cheap

Postgres is free, and open source too.

> Oracle Public Cloud gives you database extremely fast

It's extremely unlikely that devs will want to host a database in Oracle's cloud, and everything else in AWS/Azure/GCP.

> and you will never have issues with license audit

The very fact you felt the need to throw that in is exactly why people hate Oracle so much - they are absolutely infamous for screwing customers out of every cent.

> The name of "Rollback of DDLs" is "no developer access to production" and "UAT"

As others have said, it's useful for testing changes in pre-prod environments - so you can make sure stuff works before it gets to prod.

> Are you a huge fan of Vacuuming, XID Freezing, WAL optimisations etc. etc.?

This makes no sense; vacuum is automatic, and why would you not want knobs to tweak settings to your workload? Oracle has plenty, so I don't get your beef here.

> The MVCC in Postgress, in my view (!) is joke from academia, where they had not a single DBA

I've never heard a single sole claim such a thing - do you have any sources?