1. Yeah, even if you don't have 2B rows, your sequence can go past 2B because it's not affected by transaction rollbacks. This is even more of an issue if you'r

1. Yeah, even if you don't have 2B rows, your sequence can go past 2B because it's not affected by transaction rollbacks. This is even more of an issue if you're using serializable xacts, which need a retry mechanism. Much better to avoid this problem. 5. I like jsonb as a compromise. You can shove things into there, and whenever that stops making sense, you split things into their own cols/tables. The thing to watch out for is arrays within jsonb; usually not a good practice to join or do anything other than simple set/get for those. 7. Often I'm doing nodejs dev which doesn't really need Docker, so installed Postgres ends up being more convenient. Also means data persists across runs, which you may or may not want. But Docker is a better solution overall, especially at scale.