You're right that it's probably not much harder, but the current Postgres role is tied to the session, so you'll either be limited in the number of concurrent u

You're right that it's probably not much harder, but the current Postgres role is tied to the session, so you'll either be limited in the number of concurrent users (Postgres does not do great with high connection counts) or juggling SET ROLE around your connection pooling (which sounds dicey plus is just a lot of extra statements).