[postgis-users] Controlling PostGIS memory usage

[Newcomb, Doug]

FYI in Postgresql 9.3 :

https://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.3#Switch_to_Posix_shared_memory_and_mmap.28.29

"except in unusual cases, system parameters such as SHMMAX and SHMALL no
longer need to be adjusted. We need users to rigorously test and ensure
that no memory management issues have been introduced by the change."

Doug


On Thu, Mar 27, 2014 at 7:00 AM, Sandro Santilli <strk at keybit.net> wrote:

> On Wed, Mar 26, 2014 at 02:48:24PM -0500, Dan Gast wrote:
> > Hello,
> >
> > I've found a way to crash PostgreSQL by running it out of memory, and
> > after looking at the documentation I'm unable to find tuning
> > parameters to stop it.
>
> I've faced this recently, and found out it was the Linux kernel's fault.
> See http://www.etalabs.net/overcommit.html
> And "Linux Memory Overcommit" here:
> http://www.postgresql.org/docs/9.1/static/kernel-resources.html
>
> --strk;
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>



-- 
Doug Newcomb
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb at fws.gov
---------------------------------------------------------------------------------------------------------
The opinions I express are my own and are not representative of the
official policy of the U.S.Fish and Wildlife Service or Dept. of the
Interior.   Life is too short for undocumented, proprietary data formats.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20140327/4d4a9021/attachment.html>