Re: Why Wal_buffer is 64KB - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: Why Wal_buffer is 64KB
Date
Msg-id dcc563d11003282345w6d3e7adbh6458b0f5a7c3d4a6@mail.gmail.com
Whole thread Raw
In response to Re: Why Wal_buffer is 64KB  (Tadipathri Raghu <traghu.dba@gmail.com>)
Responses Re: Why Wal_buffer is 64KB
List pgsql-performance
On Mon, Mar 29, 2010 at 12:00 AM, Tadipathri Raghu <traghu.dba@gmail.com> wrote:
> Hi All,
>
> 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.

From what I understand, with fsync on or off the same stuff gets
written.  It's just not guaranteed to go out in the right order or
right now, but eventually.

pgsql-performance by date:

Previous
From: Tadipathri Raghu
Date:
Subject: Re: Why Wal_buffer is 64KB
Next
From: Tadipathri Raghu
Date:
Subject: Re: Why Wal_buffer is 64KB