Thank you for all the support.
I have noticed one more thing here, that if you turn off the fsync and try
to run the transaction than its breaking the currnet filenode and generating
another filenode. Is it true that whenever you turn off or on the fsync the
filenode will break and create one more on that table.
On Fri, Mar 26, 2010 at 7:30 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:
> On Fri, Mar 26, 2010 at 7:43 AM, Pierre C <lists(at)peufeu(dot)com> wrote:
> >> After fsync/syncronous_commit off
> > Do not use fsync off, it is not safe. Who cares about the performance of
> > fsync=off, when in practice you'd never use it with real data.
> > synchronnous_commit=off is fine for some applications, though.
> There are situations where it's ok, when all the data are
> reproduceable from other sources, etc. for instance I have a
> reporting server that is a slony slave that runs with fsync off. If
> it does crash and I can recreate the node in an hour or so and be back
> online. With fsync off the machine is too slow to do its job, and
> it's not the primary repo of the real data, so it's ok there.
In response to
pgsql-performance by date
|Next:||From: Scott Marlowe||Date: 2010-03-29 06:45:44|
|Subject: Re: Why Wal_buffer is 64KB|
|Previous:||From: Tadipathri Raghu||Date: 2010-03-29 04:56:33|
|Subject: Re: Optimizer showing wrong rows in plan|