Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id CD7EE9FB90B for ; Wed, 18 Jul 2007 16:59:08 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 65517-02-4 for ; Wed, 18 Jul 2007 16:59:02 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by postgresql.org (Postfix) with ESMTP id D40409FB66E for ; Wed, 18 Jul 2007 16:59:04 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id a2so347674ugf for ; Wed, 18 Jul 2007 12:59:03 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=uQgG/dxqxPGf6EXGDbQeD1q3Mo+4kiSZjovGnlbZ5t9b/9R9exkPx2aoopdcmxQ08iW9ex9iWTRPHHQ64J99njZ9Q8+x2ebhLbP+AWo4GohcQgCJhjYd7MRbTCJBKSrouND9kjWUhcAqvYIBSRINOoeUVJekMldlIUy+lVJUhn4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=GMpdeL8sEZ/L5MUWHTJiLjCpoMFzlKPrUVf/viP4337jM0qByXkjiVqX4H7kN/1L8UGLu/3xGP9xPn0Hof6/xYpzlON9yzmBhx86bkH92yEJi1gB1RERsbVIBmc9Vg2J0Hl3xuXrEHwUCCly40zgaJ636QTfsqCgWqDuUx/VFpI= Received: by 10.66.248.5 with SMTP id v5mr576912ugh.1184788742908; Wed, 18 Jul 2007 12:59:02 -0700 (PDT) Received: from ?192.168.1.33? ( [82.20.57.141]) by mx.google.com with ESMTPS id q40sm5986609ugc.2007.07.18.12.58.58 (version=SSLv3 cipher=RC4-MD5); Wed, 18 Jul 2007 12:58:59 -0700 (PDT) Message-ID: <469E70CA.9040302@enterprisedb.com> Date: Wed, 18 Jul 2007 20:58:02 +0100 From: Heikki Linnakangas User-Agent: Icedove 1.5.0.10 (X11/20070329) MIME-Version: 1.0 To: Adriaan van Os CC: pgsql-performance@postgresql.org Subject: Re: insert vs select into performance References: <469D1AD3.9030004@ifi.uio.no> <0D6011B2-D09F-45E8-A5D7-5F84ADD1DC2B@seespotcode.net> <5666.1184704280@sss.pgh.pa.us> <469D2D59.9030106@ifi.uio.no> <20070718113141.GH12481@mathom.us> <469E69E8.3080204@microbizz.nl> In-Reply-To: <469E69E8.3080204@microbizz.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/231 X-Sequence-Number: 25915 Adriaan van Os wrote: > So, how does one (temporarily) disable WAL logging ? Or, for example, > disable WAL logging for a temporary table ? Operations on temporary tables are never WAL logged. Operations on other tables are, and there's no way to disable it. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com