Re: Trouble Upgrading Postgres

On 11/5/18 5:56 AM, Charles Martin wrote:
> Tom said:
>
> >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.
>
> This is not a VM, but hardware.

Tom was referring to this from your previous post:

(postmaster) total-vm:3068900kB,

where vm(VM) is Virtual Memory:

https://stackoverflow.com/questions/18845857/what-does-anon-rss-and-total-vm-mean#22326766

So what is your shared_buffers:

https://www.postgresql.org/docs/10/static/runtime-config-resource.html

set to?

>
> Adrian said:
>
> >In addition to the other suggestions, what is the exact pg_dump command
> >you are using?
>
> The last time:
>
> [postgres(at)mandj tmp]$ pg_dump martinandjones >
> /mnt/4tbB/pgbackup/2018-11-02/mandj.bak
>
>
>
>
> On Sun, Nov 4, 2018 at 8:16 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
>
> On 11/4/18 2:55 PM, Charles Martin wrote:
> > 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.
> >
>
> In addition to the other suggestions, what is the exact pg_dump command
> you are using?
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com