Re: Memory-leak-like effect on insane query (postgres 8.1.6)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Brian Hurt <bhurt(at)janestcapital(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Memory-leak-like effect on insane query (postgres 8.1.6)
Date: 2008-02-11 19:32:04
Message-ID: 6658.1202758324@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Brian Hurt <bhurt(at)janestcapital(dot)com> writes:
> So, I have a couple of questions:
> 1) What can I look at to see where the memory is going? Or can someone
> just tell me?
> 2) Is there any way I can prevent someone from crashing production in
> the same way (production is 8.1.10)?

Running the postmaster under a per-process-memory ulimit setting small
enough to avoid the wrath of the OOM killer would help both of these.
(You'd get an out-of-memory error instead of kill -9, and then looking
at the memory dump in the postmaster log would help with #1.)

regards, tom lane

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message salman 2008-02-11 20:03:43 Question about CLUSTER
Previous Message Brian Hurt 2008-02-11 19:16:11 Re: Memory-leak-like effect on insane query (postgres 8.1.6)