Re: BUG #2225: Backend crash -- BIG table - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: BUG #2225: Backend crash -- BIG table
Date
Msg-id 200602030033.24848.peter_e@gmx.net
Whole thread Raw
In response to Re: BUG #2225: Backend crash -- BIG table  (Patrick Rotsaert <patrick.rotsaert@arrowup.be>)
Responses Re: BUG #2225: Backend crash -- BIG table
List pgsql-bugs
Patrick Rotsaert wrote:
> On my
> system, the parameter is 0, so overcommit is *not* enabled.

0 means overcommit is enabled.  You want to set it to something other
than 0 to prevent overcommitting and the consequent suprising process
deaths.  Exactly what other values are accepted varies, but 0 isn't the
one for you.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

pgsql-bugs by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: BUG #2231: Incorrect Order By
Next
From: Richard Huxton
Date:
Subject: Re: BUG #2232: Function (store procedure) prublem