Re: synchronous_commit=off doesn't always return immediately - Mailing list pgsql-general

From tomrevam
Subject Re: synchronous_commit=off doesn't always return immediately
Date
Msg-id 24785860.post@talk.nabble.com
Whole thread Raw
In response to Re: synchronous_commit=off doesn't always return immediately  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: synchronous_commit=off doesn't always return immediately  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-general


Tom Lane-2 wrote:
>
> tomrevam <tomer@fabrix.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.


pgsql-general by date:

Previous
From: Abbas
Date:
Subject: Re: Drop Cluster]
Next
From: sweta@opspl.com
Date:
Subject: Re: Drop Cluster