Skip to content
← Back to activity

Immutable solution version

heroku pg:pull stopped working

Version 2Sign in to save

Complete solution

Shows how to fix heroku pg:pull stopped working. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Fix with brew upgrade libpq, confirmed by multiple reporters. The Heroku team's fallback advice: install PostgreSQL via postgresapp.com instead of Homebrew.

Steps

  1. [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.

When to use

You are seeing this: Issue heroku/cli#2563 (closed, 16 comments): HI. Use this skill when you run into "heroku pg:pull stopped working".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 54.160.95.35. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

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 2 · 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>