Re: BUG #2225: Backend crash -- BIG table

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Cc: Patrick Rotsaert <patrick(dot)rotsaert(at)arrowup(dot)be>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #2225: Backend crash -- BIG table
Date: 2006-02-02 23:33:24
Message-ID: 200602030033.24848.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2006-02-03 03:55:23 Re: [BUGS] BUG #2171: Differences compiling plpgsql in ecpg
Previous Message Stephan Szabo 2006-02-02 23:13:09 Re: BUG #2231: Incorrect Order By