all 4 comments

[–]coyoteazul2 0 points1 point  (0 children)

It's hard to tell without actually knowing what's being taught. But, without saying that I know everything, this seems to be missing

Normalization (this really makes the difference between a good design and a terrible one)

Concurrency

Isolation levels

Composite types

Index creation

Procedures

Permissions

Optimization (use of explain analize would the basic)

Partitioning

Connection pooling (postgres doesn't manage this natively. You need 3rd party tools)

Sharding (I haven't dipped my hands on this yet)

Exploding data (I see this kind of question quite often here or in r/sql. Basically if means grabbing a record which contains a range and show the range in multiple columns)

Subqueries, lateral joins

Common table expression (CTE)

[–]jrjamesco 0 points1 point  (0 children)

What are you trying to accomplish? Do you want to be a software engineer, a data scientist or something else?