Re: repeated out of shared memory error - not related to max_locks_per_transaction

Fabio Pardi <f.pardi@xxxxxxxxxxxx> · Fri, 20 Jul 2018 14:47:50 +0200



    work_mem cannot be the cause of it for the simple reason that if
      the memory needed by your query overflows work_mem, it will spill
      to disk
    

    regards,
    fabio pardi
    

    On 20/07/18 14:35, MichaelDBA wrote:

    
      Perhaps your "work_mem" setting is causing the memory problems. 
      Try reducing it to see if that alleviates the problem.

      
      Regards,

      Michael Vitale

      
              Campbell, Lance
             Friday, July 20, 2018 8:32 AM
          
        
          I would also lookup the definition of shared buffers and
            effective cache. If I remember correctly you can think of
            shared buffers as how much memory total PostgreSQL has to
            work with. Effective cache is how much memory is available
            for PostgreSQL to run, shared buffers, as well as an
            estimate of how much memory is available to the OS to cache
            files in memory. So effective cache should be equal to or
            larger than shared buffers. Effective cache is used to help
            with the SQL planning.

            
            Double check the documentation. 

            
            Lance

            
            Sent from my iPad