Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Fri, 28 Apr 2006 10:59:10 +0200
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
- References:
- Re: how unsafe (or worst scenarios) when setting fsync OFF for postgresql
- From: Guoping Zhang
- Re: how unsafe (or worst scenarios) when setting fsync OFF for postgresql
- Prev by Date: Re: how unsafe (or worst scenarios) when setting fsync OFF for postgresql
- Next by Date: Re: CPU usage goes to 100%, query seems to ran forever
- Previous by thread: Re: how unsafe (or worst scenarios) when setting fsync OFF for postgresql
- Next by thread: Re: how unsafe (or worst scenarios) when setting fsync OFF for postgresql
- Indexes: