Re: Postgre Eating Up Too Much RAM

From: Fernando Hevia <fhevia(at)gmail(dot)com>
To: Aaron Bono <aaron(dot)bono(at)aranya(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Postgres <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Postgre Eating Up Too Much RAM
Date: 2012-11-14 22:51:58
Message-ID: CAGYT1XTieQp5QNCrrdwnQWdaDez7txw+i16GiSkhJTz531qqSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, Nov 14, 2012 at 2:30 AM, Aaron Bono <aaron(dot)bono(at)aranya(dot)com> wrote:

> On our old server, our hosting company said the server was running out of
> RAM and then became unresponsive. I haven't checked about the new server
> yet.

Unresponsive how? Can you ssh to it? Can you log to Postgres?
For how long does it happen? Till you reboot?
If it is a server crash then that is not a normal behavior and you should
check your hardware. An exhaustive memory test is recommended.

> Is there any kind of diagnostics you can think of that would help get to
> the root of the problem - something I could put in a cron job or a monitor
> app I could run on the server that would at least tell us what is going on
> if / when it happens again?
>
>
Increase logging on PostgreSQL. Especially log checkpoints and locks.
While experiencing the problem and if you are able to log to the server, a
vmstat 1 10 will tell you what is going on with your I/O system in a 10
second span.

Regards,
Fernando.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Shams Khan 2012-11-15 07:27:06 Query Stuck in running server
Previous Message Frank Cavaliero 2012-11-14 21:11:58 Failed Login Attempts parameter