The pitfall of using PostgreSQL advisory locks with Go's DB connection pool

Seems like if you tried to use transactions, you'd have the same problem?

TL;DR: PostgreSQL requires reserving a single connection for causally-related statements. Seems like a scaling problem for the C10K world, not just Go.