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.
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
generally not true since PG12