Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 87C0B9FB63E for ; Wed, 29 Aug 2007 16:31:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 82964-02-3 for ; Wed, 29 Aug 2007 16:31:14 -0300 (ADT) X-Greylist: delayed 00:06:39.744817 by SQLgrey-1.7.5 Received: from web31603.mail.mud.yahoo.com (web31603.mail.mud.yahoo.com [68.142.198.149]) by postgresql.org (Postfix) with SMTP id 7AD4A9F981A for ; Wed, 29 Aug 2007 16:31:16 -0300 (ADT) Received: (qmail 73363 invoked by uid 60001); 29 Aug 2007 19:24:34 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=qqgmz/5N7yRHiZMGg5WyyKl5dj4zTl+pTVBULdiStRj1BLbUEKQN3vm+//8bRSDrkJjogxk7iaPvavYI5gNlULkVGr415JJRscveBQdPIa9lm9UVgXL6a1grYtcqX4/joAR3vdrSpK8XsQe6YDTpvN/91iLarFeVSt5oWJbihmY=; X-YMail-OSG: AaPZGWcVM1lUddcvQgQxxMYYy0yu5RsU6xFv_qcAfWabFglNr1ancZn7wekoCQ5i3A-- Received: from [68.142.201.149] by web31603.mail.mud.yahoo.com via HTTP; Wed, 29 Aug 2007 12:24:34 PDT X-Mailer: YahooMailRC/651.50 YahooMailWebService/0.7.134 Date: Wed, 29 Aug 2007 12:24:34 -0700 (PDT) From: mbguy2000-1@yahoo.com Subject: Transaction Log To: pgsql-performance@postgresql.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1994608125-1188415474=:73151" Message-ID: <782718.73151.qm@web31603.mail.mud.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.002 tagged_above=0 required=5 tests=BAYES_50=0.001, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200708/383 X-Sequence-Number: 26513 --0-1994608125-1188415474=:73151 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable For best performance, the transaction log should be on a separate disk.=0A= =0ADoes=0Athe writing of the log benefit from a battery backed controller a= s=0Awell? If not, what do people think about writing the transaction log= =0Ato a flash card or the like?=0A --0-1994608125-1188415474=:73151 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable
For best performance, the transaction log should be on a separate d= isk.

Does=0Athe writing of the log benefit from a battery backed con= troller as=0Awell?  If not, what do people think about writing the tra= nsaction log=0Ato a flash card or the like?
--0-1994608125-1188415474=:73151--