X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 053A353B7C for ; Fri, 8 Apr 2005 06:38:55 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 83841-01 for ; Fri, 8 Apr 2005 05:38:46 +0000 (GMT) Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.116.145.2]) by svr1.postgresql.org (Postfix) with ESMTP id 77A6E53B61 for ; Fri, 8 Apr 2005 06:38:46 +0100 (BST) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 66D5430952; Fri, 8 Apr 2005 07:38:20 +0200 (MET DST) From: "Qingqing Zhou" X-Newsgroups: pgsql.performance Subject: Re: Compressing WAL Date: Fri, 8 Apr 2005 13:36:40 +0800 Organization: Hub.Org Networking Services Lines: 20 Message-ID: References: <20050405040457.GK93835@decibel.org> Reply-To: "Qingqing Zhou" X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.204 tagged_above=0 required=5 tests=AWL, PRIORITY_NO_NAME X-Spam-Level: * X-Archive-Number: 200504/202 X-Sequence-Number: 11599 ""Jim C. Nasby"" writes > Has anyone looked at compressing WAL's before writing to disk? On a > system generating a lot of WAL it seems there might be some gains to be > had WAL data could be compressed before going to disk, since today's > machines are generally more I/O bound than CPU bound. And unlike the > base tables, you generally don't need to read the WAL, so you don't > really need to worry about not being able to quickly scan through the > data without decompressing it. > -- The problem is where you put the compression code? If you put it inside XLogInsert lock or XLogWrite lock, which will hold the lock too long? Or anywhere else? Regards, Qingqing