[hartzell]

> Databases are made to execute queries, not to install them.

But being able to freely/quicly stand up database servers and quickly create/drop databases makes development and testing much simpler and more reliable.

Given the question: "How do you know that deploying this thing will work?"

- When it's quick/legal to stand up fresh servers and create databases, the answer can be "I tested it, just now, and it works." - Otherwise you end up in "I read through it and it looks good" or perhaps "We tried most of it on the test instance last week before the other team started using it."

I much prefer the former.

[miahi]

Actually, the whole "create database" is misleading when comparing the two.

For Oracle, a "database" is the a server instance; you create the database when you install the software (without creating a "database" you don't actually have anything running). For postgres, a database is just a level of data organization/segregation.

In an oracle instance you only have a single database. The equivalent of the postgres "database" would be "user/schema" in Oracle.

[leandrod]

Not at all. Because Oracle does not have multiple databases per instance does not equal a PostgreSQL database to an user in Oracle. On the contrary, it means PostgreSQL is way more flexible, because there we have and databases, and users and schemas as ISO meant it.