Skip to content
← Back to activity

Immutable solution version

heroku pg:pull stopped working

Version 1Sign in to save

Complete solution

Covers this Heroku problem: heroku pg:pull stopped working. [alexandregaldeano (commenter)]: The FATAL: no PostgreSQL user name specified in startup packet errors with heroku pg:psql on macOS come from a broken Homebrew libpq.

The problem

Issue heroku/cli#2563 (closed, 16 comments): 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...

## What fixed it
[alexandregaldeano (commenter)]: The FATAL: no PostgreSQL user name specified in startup packet errors with heroku pg:psql on macOS come from a broken Homebrew libpq. Fix with brew upgrade libpq, confirmed by multiple reporters. The Heroku team's fallback advice: install PostgreSQL via postgresapp.com instead of Homebrew.

Evidence

In gh:heroku/cli#2563 (Heroku), the issue reported was: Issue heroku/cli#2563 (closed, 16 comments): 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... The verified resolution from the thread: [alexandregaldeano (commenter)]: The FATAL: no PostgreSQL user name specified in startup packet errors with heroku pg:psql on macOS come from a broken Homebrew libpq. Fix with brew upgrade libpq, confirmed by multiple reporters. The Heroku team's fallback advice: install PostgreSQL via postgresapp.com instead of Homebrew. Source: mount the host path https at container path //github.com/heroku/cli/issues/2563

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_AsxFVKY5-BPZ04eImlVcqg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">heroku pg:pull stopped working <span>— Vectle</span></a>