Re: BUG #13637: ~2 GB psql import fails with out of memory error on machine with 64 GB RAM

psql was definitely using up the most memory--but like I said, the
total memory usage on the server was ~10 GB. There was approximately
54 GB free the entire time.

A few options:

* I can put the DB on my server and send you an HTTP URL
* You can send me an SSH public key and do rsync or sftp
* I can stick it in a folder and send you a bitsync key

I have no preference. The DB probably doesn't contain anything
private, but it could contain a few dev passwords. Quite a few of
them have been changed since I decided to have an impromptu test of my
backups. ;)

-A

On Thu, Sep 24, 2015 at 9:17 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> aaron(at)heyaaron(dot)com writes:
>> I tried importing again with the swap file in-place, and it consumed all the
>> memory and crashed. I tried disabling swap, starting psql, then enabling
>> swap and I was able to restore the same majority of tables.
>
> That's odd. Was it psql itself that was exhausting memory, or the
> connected backend?
>
>> I do have the ~2.3 GB backup of the DB which bzip's down to ~550 MB if any
>> developers are interested in playing/testing.
>
> That sounds too big for email, but if you have another way to get it
> to me, I'd take a look.
>
> regards, tom lane