[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-bugs
Subject:    Re: [BUGS] statement_timeout is not cancelling query
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2009-12-15 20:52:53
Message-ID: 14144.1260910373 () sss ! pgh ! pa ! us
[Download RAW message or body]

Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Dec 15, 2009 at 3:45 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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?

Should be an ERROR ... if it isn't, that's probably a bug.  The design
intention is that malloc failure is just an ERROR.

			regards, tom lane

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
[prev in list] [next in list] [prev in thread] [next in thread]