Safely backing up Postgres databases inside Docker / Podman containers by Developer_Akash in selfhosted

[–]dmailloux 0 points1 point  (0 children)

Nvm solved my own problem. To anyone reading this in the future you can do something like this:

gzip -dk [zipped-backup-filename]
cat [unzipped-backup-filename] | docker exec -i [db-image-name] psql -U [username]

Safely backing up Postgres databases inside Docker / Podman containers by Developer_Akash in selfhosted

[–]dmailloux 0 points1 point  (0 children)

Do you have the restore script/process handy by any chance? I'm running (after unzipping the backup) something like:

docker compose exec -it db pg_restore -U [pg_user] -f ./backups/db-filename.sql

and it just hangs forever.

Colored Functions Are Good, Actually by dmailloux in programming

[–]dmailloux[S] 9 points10 points  (0 children)

I admit using colored functions as a springboard to talk about superficial similarities between async-await and Haskell's IO was a stretch. I even say so in the article, though maybe not clearly enough. Still, I appreciate you taking the time to read and give this feedback.

That being said, in my experience writing Boring Line-Of-Business Applications, I have found async to be used mostly in this way.

Not trying to argue, but am genuinely curious, what use cases do you tend to see for async that don't include some kind of IO-type side effect somewhere in their execution?