From: Markus Schaber <schabi@logix-tt.com>
To: pgsql-performance@postgresql.org
Cc: guoping.zhang@nec.com.au
Subject: Re: how unsafe (or worst scenarios) when setting fsync
Date: Fri, 28 Apr 2006 10:59:10 +0200
Message-ID: <4451D95E.9080308@logix-tt.com> (raw)
In-Reply-To: <004101c66a7e$4ab95000$74304c93@eddy>
References: <004101c66a7e$4ab95000$74304c93@eddy>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: schabi@logix-tt.com, guoping.zhang@nec.com.au
Subject: Re: how unsafe (or worst scenarios) when setting fsync
In-Reply-To: <4451D95E.9080308@logix-tt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox