| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Charles Martin <ssappeals(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Trouble Upgrading Postgres |
| Date: | 2018-11-04 23:19:15 |
| Message-ID: | 22658.1541373555@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Charles Martin <ssappeals(at)gmail(dot)com> writes:
> Yep, you called it:
> Nov 2 20:30:45 localhost kernel: Out of memory: Kill process 30438
> (postmaster) score 709 or sacrifice child
> Nov 2 20:30:45 localhost kernel: Killed process 30438, UID 26,
> (postmaster) total-vm:3068900kB, anon-rss:1695392kB, file-rss:1074692kB
> So it's running out of memory when trying to dump this table. The "old"
> server has 4GB of ram, the "new" server 20GB.
That's kind of odd: a COPY shouldn't really consume very much working
memory. I suspect that much of the process's apparent VM consumption may
be shared buffers ... what have you got shared_buffers set to on the old
server? If it's more than half a GB or so, maybe reducing it would help.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2018-11-05 01:16:34 | Re: Trouble Upgrading Postgres |
| Previous Message | Ron | 2018-11-04 23:00:59 | Re: Trouble Upgrading Postgres |