Explore >> Select a destination
|
You are here 
|
codeinthehole.com | ||
| | | | |
blog.keikooda.net
|
|
| | | | | This post is super outdated | |
| | | | |
blog.hypriot.com
|
|
| | | | | ||
| | | | |
mattray.github.io
|
|
| | | | | You've somehow ended up reading Matt Ray's ramblings. | |
| | | | |
jinyuz.dev
|
|
| | | So, I was trying to reproduce some issues and bugs that only happened in production. I needed an exact copy of the production database and run it locally. Here's how I did it using pg_dump and pg_restore. $ pg_dump -U postgres -Fc -Z 9 -j 8 production.dump -d postgres Here's the breakdown for the arguments: U means username. It's used to connect to your postgres database. In this case, my username is postgres. | ||
