cli: heroku pg:pull stopped working
HI.
This week the heroku pg:pull command stopped working and it returns:
heroku-cli: Pulling postgresql-metric-35199 ---> aposta10_development
pg_dump: error: connection to server at "ec2-54-160-95-35.compute-1.amazonaws.com" (54.160.95.35), port 5432 failed: FATAL: no PostgreSQL user name specified in startup packet
connection to server at "ec2-54-160-95-35.compute-1.amazonaws.com" (54.160.95.35), port 5432 failed: FATAL: no PostgreSQL user name specified in startup packet
pg_restore: error: could not read from input file: end of file
▸ pg_dump errored with 1
I’m using the latest MacOS and it has been working well until this week. If a new credential is required now, where do I have to add it?
I’ll appreciate any help.
Thanks.
About this issue
- Original URL
- State: closed
- Created 7 months ago
- Comments: 16 (7 by maintainers)
I had the same issue with PostgreSQL 16.0, doing
brew upgrade libpqfixed it. See https://github.com/Homebrew/homebrew-core/issues/155651#issuecomment-1828065418Thanks for the update, I hope you’re able to get the problem resolved. I’m going to go ahead and close this issue for now, but please reopen in the future if needed.
@k80bowman makes sense and sounds good! Thanks for the help.
I’ve got a Fedora Linux computer I use too and thought I’d do some more testing. The
heroku pg:psqlcommand works. I ran all the tests you provided on Heroku CLI v8.7.1 and it’s all working as expected:psql --versionoutputspsql (PostgreSQL) 15.4psqldirectlyso maybe it’s an issue with psql v14.X on macOS specifically? That’d make sense given the debugging and info.
I’m also experiencing this issue.
Mac OS Sonoma 14.1.1