Re: Log full with gigabyes of CurTransactionContex

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Iñigo Martinez Lasala <imartinez(at)vectorsf(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Log full with gigabyes of CurTransactionContex
Date: 2009-06-15 15:23:45
Message-ID: 16564.1245079425@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

=?ISO-8859-1?Q?I=F1igo?= Martinez Lasala <imartinez(at)vectorsf(dot)com> writes:
> We have increased shared buffers to 2.5GB (linux kernels allows us reach
> this level) and lowered work_mem to 500MB.

You are apparently unclear on the concept. Pushing the database to the
limit of the available address space is probably going to result in
failures. Redistributing a set of overoptimistic parameters into a
different set of overoptimistic parameters will not fix this.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Iñigo Martinez Lasala 2009-06-15 15:51:33 Re: Log full with gigabyes of CurTransactionContex
Previous Message Gurjeet Singh 2009-06-15 15:18:41 Re: Log full with gigabyes of CurTransactionContex