Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id B117E9FBB40 for ; Tue, 3 Apr 2007 16:40:07 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 78224-08 for ; Tue, 3 Apr 2007 16:40:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by postgresql.org (Postfix) with ESMTP id DC45E9FBB13 for ; Tue, 3 Apr 2007 16:40:01 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id k3so387936ugf for ; Tue, 03 Apr 2007 12:40:00 -0700 (PDT) Received: by 10.67.50.7 with SMTP id c7mr859996ugk.1175629200089; Tue, 03 Apr 2007 12:40:00 -0700 (PDT) Received: from ?192.168.0.174? ( [88.232.58.149]) by mx.google.com with ESMTP id e23sm1636634ugd.2007.04.03.12.39.57; Tue, 03 Apr 2007 12:39:59 -0700 (PDT) Message-ID: <4612AD87.1040406@netsyncro.com> Date: Tue, 03 Apr 2007 22:39:51 +0300 From: =?ISO-8859-1?Q?=22C=2E_Bergstr=F6m=22?= User-Agent: Thunderbird 1.5.0.10 (X11/20070309) MIME-Version: 1.0 CC: pgsql-performance@postgresql.org Subject: Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000" References: <4612A421.4060808@andromeiberica.com> <4612A57B.2030601@agliodbs.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.715 tagged_above=0 required=5 tests=BAYES_20=-0.74, RCVD_IN_SORBS_WEB=1.456, SPF_PASS=-0.001 X-Spam-Level: X-Archive-Number: 200704/30 X-Sequence-Number: 23907 A.M. wrote: > Indeed... I looked through the official TODO list and was unable to > find an entry for global temporary tables- such a thing would be ideal > for any transient data such as web sessions or materialized views. Is > there any reason why global temp tables shouldn't be implemented? > (And, no, I'm not simply referring to "in-memory" tables- they can > simply be handled with a ram disk.) Not exactly what you're looking for and a simple API, but the performance is very nice and has a lot of potential. http://pgfoundry.org/projects/pgmemcache/ Implementing a cleaner more transparent sql wrapper would be even nicer. http://tangent.org/index.pl?lastnode_id=478&node_id=506 Just sharing/tossing some ideas around.. C.