Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 12F87633266
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Tue, 30 Mar 2010 11:43:43 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia,
	port 10024) with ESMTP id 11267-07
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Tue, 30 Mar 2010 14:43:20 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-fx0-f225.google.com (mail-fx0-f225.google.com
	[209.85.220.225])
	by mail.postgresql.org (Postfix) with ESMTP id A2DB06326BA
	for <pgsql-performance@postgresql.org>;
	Tue, 30 Mar 2010 11:43:29 -0300 (ADT)
Received: by fxm25 with SMTP id 25so30657fxm.3
	for <pgsql-performance@postgresql.org>;
	Tue, 30 Mar 2010 07:43:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:received:message-id:subject:from:to:cc:content-type;
	bh=rqJ0rZ3CFa2VamtXJYTdqu23GQYxkhGnPiR4bARI9S8=;
	b=gA0px7Aeb2iR/W2FmV56rVIfZTdw75d7dT5vLnn3MqM8/mE9y2X+Cpt7nY/uRMeiiL
	PxmHQvLRqN99fCIjSupC4Wf6q/jeAfXnbl980m9pYlYOayEMck4ceuG7tIwdtuykoOvW
	9eRArYhtrey+YePuxBwXvJrt2nZgTPQXvevVA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	b=pjJ5KKvXwdauYBnm37etQtDI5Pjlo10D0jw6YJv8b/QtleVvnXpS0MpXzWsy+RciwN
	VHrYqI2x9T7v2fa5ovExcuodx4Fzc6UlXg+Yip2tkEEGO+TXIWSqU7il2JroHMBQGwzC
	DNjPbvU6KTYruUZpVr3fm1rz1hlQBIpkUz13c=
MIME-Version: 1.0
Received: by 10.239.161.83 with HTTP; Tue, 30 Mar 2010 07:43:27 -0700 (PDT)
In-Reply-To: <645d9d71003282300j6ef4a9d5pbfa257667e6a7e3a@mail.gmail.com>
References: <645d9d71003250801o246439a0j93c7b568786e98de@mail.gmail.com>
	<3073cc9b1003251015x590e962ata59dadbb58b42ce5@mail.gmail.com>
	<op.u94yaoixeorkce@localhost>
	<645d9d71003252019u6f01a513x7876c1a97b448dea@mail.gmail.com>
	<op.u96ge7lfeorkce@localhost>
	<dcc563d11003260700i71f4c974o27b3f1db2f9ef609@mail.gmail.com>
	<645d9d71003282300j6ef4a9d5pbfa257667e6a7e3a@mail.gmail.com>
Date: Tue, 30 Mar 2010 10:43:27 -0400
Received: by 10.239.180.200 with SMTP id j8mr591169hbg.166.1269960207382;
 Tue,
	30 Mar 2010 07:43:27 -0700 (PDT)
Message-ID: <603c8f071003300743q4a63ebf4t514c27e067500939@mail.gmail.com>
Subject: Re: Why Wal_buffer is 64KB
From: Robert Haas <robertmhaas@gmail.com>
To: Tadipathri Raghu <traghu.dba@gmail.com>
Cc: Scott Marlowe <scott.marlowe@gmail.com>, Pierre C <lists@peufeu.com>,
	Jaime Casanova <jcasanov@systemguards.com.ec>,
	pgsql-performance@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.482 tagged_above=-10 required=5 tests=AWL=0.117,
	BAYES_00=-2.599
X-Spam-Level: 
X-Archive-Number: 201003/387
X-Sequence-Number: 38212

On Mon, Mar 29, 2010 at 2:00 AM, Tadipathri Raghu <traghu.dba@gmail.com> wrote:
> 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.

I don't know what you mean by a filenode.  Changing the fsync
parameter doesn't cause any additional files to be created or written.

...Robert