From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Edson Richter <edsonrichter(at)hotmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Invalid memory alloc |
Date: | 2015-04-23 20:34:28 |
Message-ID: | 55395754.6080803@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 4/23/15 3:15 PM, Edson Richter wrote:
> My question would sound stupid... you have 10Gb shared buffer, but how
> much physical memory on this server?
> How have you configured the kernel swappines, overcommit_memoryt,
> overcommit_ratio?
> Have you set anything different in shmmax or shmall?
I don't think this is an OS thing at all. That error messages is pretty
associated with this code:
#define MaxAllocSize ((Size) 0x3fffffff) /* 1 gigabyte - 1 */
#define AllocSizeIsValid(size) ((Size) (size) <= MaxAllocSize)
If malloc failed you'd get an actual out of memory error, not a notice.
We need more information from the OP about what they're doing.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-04-23 20:44:27 | Re: Invalid memory alloc |
Previous Message | Jim Nasby | 2015-04-23 20:27:38 | Re: Moving Specific Data Across Schemas Including FKs |