X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4535FD8D6F for ; Wed, 14 Sep 2005 14:04:20 -0300 (ADT) 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 74125-10 for ; Wed, 14 Sep 2005 17:04:15 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 08B49D7152 for ; Wed, 14 Sep 2005 14:04:12 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j8EH47QM094440 for ; Wed, 14 Sep 2005 17:04:09 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j8EGlxbk084191 for pgsql-admin@postgresql.org; Wed, 14 Sep 2005 16:47:59 GMT (envelope-from news) From: William Yu X-Newsgroups: pgsql.admin Subject: Re: Disabling WAL for bulk data loads Date: Wed, 14 Sep 2005 09:47:54 -0700 Organization: Hub.Org Networking Services Lines: 11 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en In-Reply-To: To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=-2.605 required=5 tests=[ALL_TRUSTED=-2.82, AWL=0.215] X-Spam-Level: X-Archive-Number: 200509/164 X-Sequence-Number: 18901 Kevin Keith wrote: > I am coming from an Oracle background - which in the case of bulk data > loads there were several options I had where I could disable writing to > the redo log to speed up the bulk data load (i.e. direct load, set the > user session in no archive logging, set the affected tables to have no > logging). If you have enough memory, you can always make a ramdisk to store the WAL temporarily while you bulk load data. I also temporarily alter the config to set checkpoint_segments = 1 to use as few pg_xlog files as possible.