Skip site navigation (1) Skip section navigation (2)

Re: how unsafe (or worst scenarios) when setting fsync

From: Markus Schaber <schabi(at)logix-tt(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Cc: guoping(dot)zhang(at)nec(dot)com(dot)au
Subject: Re: how unsafe (or worst scenarios) when setting fsync
Date: 2006-04-28 08:59:10
Message-ID: 4451D95E.9080308@logix-tt.com (view raw or flat)
Thread:
Lists: pgsql-performance
Hk, Guoping,

Guoping Zhang wrote:

> a) The tests consists of ten thousands very small transactions, which are
> not grouped, that is why so slow with compare to set fsync off.

If those transactions are submitted by concurrent applications over
several simulataneous connections, playing with commit_delay and
commit_siblins may improve your situation.

HTH,
Markus

-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org

In response to

pgsql-performance by date

Next:From: AndrusDate: 2006-04-28 09:00:35
Subject: Re: CPU usage goes to 100%, query seems to ran forever
Previous:From: Mikael CarneholmDate: 2006-04-28 08:51:22
Subject: Re: how unsafe (or worst scenarios) when setting fsync OFF for postgresql

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group