Cannot allocate memory - Mailing list pgsql-hackers

From Heng Zhi Feng (zheng@hsr.ch)
Subject Cannot allocate memory
Date
Msg-id CADBC8F358BE2845B978CF56956066AF04F60F71@SID00202.hsr.ch
Whole thread Raw
Responses Re: Cannot allocate memory  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-hackers
<div class="WordSection1"><p class="MsoNormal"><span lang="EN-US">Hi,</span><p class="MsoNormal"><span
lang="EN-US"> </span><pclass="MsoNormal"><span lang="EN-US">We have a problem where PostgreSQL will restart or shutdown
whencalling it through PDAL write filter. This was after we applied pgtune on the postgresql.conf.</span><p
class="MsoNormal"><spanlang="EN-US"> </span><p class="MsoNormal"><u><span lang="EN-US">These are the settings on the
machine:</span></u><pclass="MsoNormal"><span lang="EN-US">Virtual Machine – Ubuntu 13.10</span><p
class="MsoNormal"><spanlang="EN-US">1.92GB Memory</span><p class="MsoNormal"><span lang="EN-US">2 Parallel
Processors</span><pclass="MsoNormal"><span lang="EN-US"> </span><p class="MsoNormal"><span lang="EN-US">And these are
theconfigurations from pgtune:</span><p class="MsoNormal"><span
lang="EN-US">#------------------------------------------------------------------------------</span><p
class="MsoNormal"><spanlang="EN-US"># CUSTOMIZED OPTIONS</span><p class="MsoNormal"><span
lang="EN-US">#------------------------------------------------------------------------------</span><p
class="MsoNormal"><spanlang="EN-US">default_statistics_target = 50                   # pgtune wizard
2013-11-14</span><pclass="MsoNormal"><span lang="EN-US">maintenance_work_mem = 112MB       # pgtune wizard
2013-11-14</span><pclass="MsoNormal"><span lang="FR-CH">constraint_exclusion = on                           # pgtune
wizard2013-11-14</span><p class="MsoNormal"><span lang="EN-US">checkpoint_completion_target = 0.9     # pgtune wizard
2013-11-14</span><pclass="MsoNormal"><span lang="EN-US">effective_cache_size = 1408MB               # pgtune wizard
2013-11-14</span><pclass="MsoNormal"><span lang="EN-US">work_mem = 11MB                                      # pgtune
wizard2013-11-14</span><p class="MsoNormal"><span lang="EN-US">wal_buffers = 8MB                                       
 #pgtune wizard 2013-11-14</span><p class="MsoNormal"><span lang="EN-US">checkpoint_segments = 16
                       # pgtune wizard 2013-11-14</span><p class="MsoNormal"><span lang="EN-US">shared_buffers =
448MB                           # pgtune wizard 2013-11-14</span><p class="MsoNormal"><span
lang="EN-US">max_connections= 80                                  # pgtune wizard 2013-11-14</span><p
class="MsoNormal"><spanlang="EN-US">                                                               </span><p
class="MsoNormal"><spanlang="EN-US">I have also set the shmmax to a higher value to adapt to the new configurations but
itdoes not seem to solve the problem.</span><p class="MsoNormal"><span lang="EN-US"> </span><p
class="MsoNormal"><u><spanlang="EN-US">Below is a snippet of the postgresql.log:</span></u><p class="MsoNormal"><span
lang="EN-US">2013-11-1511:02:35 CET LOG:  could not fork autovacuum worker process: Cannot allocate memory</span><p
class="MsoNormal"><spanlang="EN-US">2013-11-15 11:02:36 CET LOG:  could not send data to client: Broken pipe</span><p
class="MsoNormal">2013-11-1511:02:36 CET LOG:  unexpected EOF on client connection<p class="MsoNormal"> <p
class="MsoNormal">Thanks<pclass="MsoNormal"> <p class="MsoNormal">Zhi Feng</div> 

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: init_sequence spill to hash table
Next
From: Sawada Masahiko
Date:
Subject: Re: Logging WAL when updating hintbit