From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | aaron(at)heyaaron(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #13637: ~2 GB psql import fails with out of memory error on machine with 64 GB RAM |
Date: | 2015-09-25 04:17:31 |
Message-ID: | 22219.1443154651@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Aaron C. de Bruyn | 2015-09-25 04:22:47 | Re: BUG #13637: ~2 GB psql import fails with out of memory error on machine with 64 GB RAM |
Previous Message | Tom Lane | 2015-09-25 04:06:31 | Re: BUG #13636: psql numericlocale adds comma where it ought not |