top | item 34016780

(no title)

Tsarbomb | 3 years ago

They for some reason are refusing to prove the affirmative of their statement that there are things Oracle can do that Postgres cannot; which leads back to my original question, that they may simply not know Postgres.

discuss

order

slt2021|3 years ago

1. oracle's query planner/optimizer is smarter and more efficient, especially with complex query. postgres for quite some time did not do well with nested, lateral queries with CTEs that include views - it's performance would randomly degrade on complex queries, which is rarer thing in oracle world.

CTE expression is an optimization fence in postgres, which is not the case in oracle.

2. oracle does not need vacuum, unlike postgres

3. postgres has problems with many concurrent connections, thats why you need workarounds like pgbouncer. Oracle doesnt need that.

And same picture with almost any other feature - it is sort of "works" in postgres - but with crutches/workarounds, while in Oracle - stuff just works out of the box.

You dont need to search and install some obscure opensource extension to get the thing you want working, like you do in postgres world. and then keep updating that extension with every new version, etc

scalatohaskell|3 years ago

> CTE expression is an optimization fence in postgres, which is not the case in oracle.

generally not true since PG12

Tsarbomb|3 years ago

Just curious how you are certain of the better performance and behaviour of Oracle given that Oracle does not allow disclosing of benchmarks without prior consent from them?

braingenious|3 years ago

I think they mentioned SQL modelling being part of the core software.