So I have tried to use Dropbox and other services, but I had the same error until the tenth attempt. Here is what I did:
I logged in to my with my Heroku cli from my terminal on the master branch so I don't have to redefine the app. (specify the path to your damp. I have mine on the same directory) e.g:
the I run
I had also a similar case and I solved it via doing theese steps:
First of all I made an initial psql_dump with the tables I wanted to dump:
pg_dump -t my_table1 -t mytable2 > my_dump.sql
Then I listed any sequence existing by filtering them, from the existing dump I made. In case of larger dumps use tools offered in bash or in powershell in order to ...
I have encountered the same issue while trying to restore some dumps, in -Fc custom format. I'm not sure the problem will or can occur with any of the other dump formats.
However, I found that the "out of memory" error that pg_restore laconically drops on exit, is program-internal and not actually an OOM. It also occured without any DB interaction, when '...