PostgreSQL kinda mimics the oracle way, though it only goes so far. The default definition of PostgreSQL's search_path is: "$user", public So if a schema was

PostgreSQL kinda mimics the oracle way, though it only goes so far. The default definition of PostgreSQL's search_path is: "$user", public So if a schema was named the same as the user, you'd automatically have objects available without qualification. I spent about a fair amount of time working with Oracle and it forces the paradigm of a schema meaning user much more than does PostgreSQL... though with some effort you can make it work somewhat like the logical namespacing capability that PostgreSQL schemas are used for.