Re: synchronous_commit=off doesn't always return immediately

From: tomrevam <tomer(at)fabrix(dot)tv>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: synchronous_commit=off doesn't always return immediately
Date: 2009-08-03 06:14:58
Message-ID: 24785860.post@talk.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane-2 wrote:
>
> tomrevam <tomer(at)fabrix(dot)tv> writes:
> It might help to increase wal_buffers.
>

Hi,

I increased the wal_buffers to 2 MB. Initially this improved the performance
very much, but after 4 days of continuous operation the system is back to
very long inserts and updates (at least as bad as it was before).
Is there a way to know what resource the DB is running out of?

Thanks,
Tomer
--
View this message in context: http://www.nabble.com/synchronous_commit%3Doff-doesn%27t-always-return-immediately-tp24621119p24785860.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message sweta 2009-08-03 06:24:52 Re: Drop Cluster
Previous Message Abbas 2009-08-03 05:46:01 Re: Drop Cluster]