Received: from maia.hub.org (maia-4.hub.org [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 78DFA633140 for ; Tue, 25 May 2010 06:00:32 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 26824-08 for ; Tue, 25 May 2010 09:00:24 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from www64.your-server.de (www64.your-server.de [213.133.104.64]) by mail.postgresql.org (Postfix) with ESMTP id DBD8263311C for ; Tue, 25 May 2010 06:00:24 -0300 (ADT) Received: from [78.46.5.203] (helo=sslproxy01.your-server.de) by www64.your-server.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1OGpzr-0006qh-Ie; Tue, 25 May 2010 11:00:23 +0200 Received: from [217.89.104.238] (helo=lisa.local.iathh.de) by sslproxy01.your-server.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1OGqSu-00053C-3j; Tue, 25 May 2010 11:30:24 +0200 Received: from [10.22.0.6] ([10.22.0.6]) (authenticated user joachim.worringen@iathh.de) by lisa.local.iathh.de (Kerio MailServer 6.7.3 patch 1); Tue, 25 May 2010 11:00:15 +0200 Message-ID: <4BFB91A8.20805@iathh.de> Date: Tue, 25 May 2010 11:00:24 +0200 From: Joachim Worringen Organization: IAT GmbH User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: =?UTF-8?B?R3J6ZWdvcnogSmHFm2tpZXdpY3o=?= CC: pgsql-performance@postgresql.org Subject: Re: performance of temporary vs. regular tables References: <4BFB837C.6010005@iathh.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Authenticated-Sender: office@iathh.de X-Virus-Scanned: Clear (ClamAV 0.96/11075/Tue May 25 01:21:58 2010) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201005/167 X-Sequence-Number: 38751 Am 25.05.2010 10:49, schrieb Grzegorz Jaśkiewicz: > temporary tables are handled pretty much like the regular table. The > magic happens on schema level, new schema is setup for connection, so > that it can access its own temporary tables. > Temporary tables also are not autovacuumed. > And that's pretty much the most of the differences. Thanks. So, the Write-Ahead-Logging (being used or not) does not matter? And, is there anything like RAM-only tables? I really don't care whether the staging data is lost on the rare event of a machine crash, or whether the query crashes due to lack of memory (I make sure there's enough w/o paging) - I only care about performance here. Joachim