I have run this command a thousand times and it worked until some days ago. I run

Thanks <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-u

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

heroku pg:pull ignoring PGPORT when calling `createdb` about legacy-cli HOT 2 OPEN

Alain1405 commented on June 23, 2024

heroku pg:pull ignoring PGPORT when calling `createdb`

from legacy-cli.

Comments (2)

Alain1405 commented on June 23, 2024 2

Thanks @ransombriggs , that definitely fixed it partially. Now the PGPORT env variable is honored.
However I now get, at the end of the procedure:

psql: server does not support SSL, but SSL was required
 ▸    WARNING: Extensions in newly created target database differ from existing source database.
 ▸    Target extensions:
 ▸    
 ▸    Source extensions:
 ▸    extname
 ▸    ---------
 ▸    plpgsql
 ▸    (1 row)
 ▸    
 ▸    
 ▸    HINT: You should review output to ensure that any errors
 ▸    ignored are acceptable - entire tables may have been missed, where a dependency
 ▸    could not be resolved. You may need to to install a postgresql-contrib package
 ▸    and retry.
heroku-cli: Pulling complete.

I don't understand if the SSL message and the extension message are related. For sure after all pg_dums and pg_restores the local db is not in place. I'm figuring out how to debug it.

Btw, I'm on OSX 10.12

from legacy-cli.