Re: Running out of memory at vacuum

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Ioana Danes <ioanasoftware(at)yahoo(dot)ca>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Running out of memory at vacuum
Date: 2013-05-16 13:56:07
Message-ID: CAMkU=1wFmr6t1QCVvixXDBMspM56vR_Ue1gWFrVW94dhwKjj4g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, May 16, 2013 at 6:35 AM, Ioana Danes <ioanasoftware(at)yahoo(dot)ca> wrote:

> Hi Jeff,
>
> On Tuesday, May 14, 2013, Ioana Danes wrote:
>
>
> The fix is to restart postgres ... If I only close the connections the
> problem is still these so I need to restart postgres.
>
>
> How are you closing the connections?
>
> I restart the application server. The problem is that the max_idle
> connections was set to 1000 on jdbc connection so once the spike happened
> the app would run with 300 connections and 250 of them or so IDLE for most
> of the time. I am fixing that
>

Hi Ionana, thanks for the responses. Does restarting the app server
successfully cause all of those connections to terminate? If so, and yet
you still have memory problems, then there is still the mystery of where
the memory is going.

Cheers,

Jeff

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message JotaComm 2013-05-16 14:12:28 WAL contains references to invalid pages
Previous Message Tom Lane 2013-05-16 13:45:32 Re: Schema (Search path issue) on PostgreSQL9.2