Stephen Frost <sfrost@xxxxxxxxxxx> writes: > * Matt Magoffin (postgresql.org@xxxxxxx) wrote: >> Yes... and indeed changing vm.overcommit_ratio to 80 does allow that >> previously-failing query to execute successfully. Do you think this is >> also what caused the out-of-memory error we saw today just when a >> transaction was initiated? > Almost certainly.. You were running close to the edge *system-wide* on > memory allocations based on your meminfo results. You'll want to keep > an eye on the limit vs. the committed amount going forward so as to > avoid this happening in the future. It's just about the same as > watching how you're doing on overall memory usage in the box or on swap > usage. Set up some nagios monitoring, and alarm once > Committed_As/CommitLimit goes over 90%. IIRC, our documentation points out vm.overcommit_memory as a critical parameter, but says nothing about overcommit_ratio nor how to find out how close you are to hitting that limit. Without necessarily being prescriptive about the best strategy, should we add some info to let people know about these things? This thread was mostly news to me, so I suspect it's news to some other folk as well. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
