Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.4) with SMTP id f7KEJ3P33013 for ; Mon, 20 Aug 2001 10:19:03 -0400 (EDT) (envelope-from pgsql-sql-owner@postgresql.org) Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7F3wLP37495 for ; Tue, 14 Aug 2001 23:58:22 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f7F3vvY24383; Tue, 14 Aug 2001 23:57:57 -0400 (EDT) To: Paul McGarry cc: "'pgsql-sql@postgresql.org'" Subject: Re: Temp tables being written to disk. Avoidable? In-reply-to: References: Comments: In-reply-to Paul McGarry message dated "Wed, 15 Aug 2001 11:12:47 +1000" Date: Tue, 14 Aug 2001 23:57:57 -0400 Message-ID: <24380.997847877@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200108/241 X-Sequence-Number: 4473 Paul McGarry writes: > Can I avoid having the temp table written to disk Not at present --- temp tables are not different from real tables, except for some naming shenanigans. So creation of a temp table will involve some disk hits. Do you really *need* a temp table, as opposed to writing a sub-SELECT-in-the-FROM-clause? ISTM that that feature takes care of most of the simple notational reasons for wanting a temp table. regards, tom lane