Skip site navigation (1) Skip section navigation (2)

Re: statement_timeout is not cancelling query

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Mark Williamson <thetazzbot(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: statement_timeout is not cancelling query
Date: 2009-12-15 20:46:22
Message-ID: 603c8f070912151246n623fb837tfb3e44db1a94ac44@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Tue, Dec 15, 2009 at 3:45 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Err, sorry, I quoted the wrong part.  I meant, how would you rlimit
>> the server memory usage?
>
> Put a ulimit command in the server start script?  Depending on the
> details of the start script you might need to put it in the postgres
> user's .profile instead, but it's certainly doable.

This may be a stupid question, but when you hit the limit, will it
result in an ERROR or a PANIC?

...Robert

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-12-15 20:52:53
Subject: Re: statement_timeout is not cancelling query
Previous:From: Tom LaneDate: 2009-12-15 20:45:40
Subject: Re: statement_timeout is not cancelling query

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group