Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 90145476367 for ; Tue, 8 Oct 2002 12:15:18 -0400 (EDT) Received: from mail.tpchd.org (unknown [192.103.155.40]) by postgresql.org (Postfix) with SMTP id 56A6F476366 for ; Tue, 8 Oct 2002 12:15:17 -0400 (EDT) Received: from TPC-Message_Server by mail.tpchd.org with Novell_GroupWise; Tue, 08 Oct 2002 09:15:16 -0700 Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.2.1 Date: Tue, 08 Oct 2002 09:13:23 -0700 From: "Ian Harding" To: Subject: Re: Temporary tables and indexes Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/111 X-Sequence-Number: 9828 Sure there is! There are queries that benefit from having a temporary tab= le created for a subquery and the temporary table indexed before the join. = Since we can't easily return result sets from functions yet, it's not prob= ably used that much, but from within a function, I can see why you might wa= nt to do this from time to time. Ian A. Harding Programmer/Analyst II Tacoma-Pierce County Health Department (253) 798-3549 iharding@tpchd.org WWSD - What Would Scooby Doo? >>> "Josh Berkus" 10/08/02 08:36AM >>> Ludwig, > Are the indices of a temporary table automatically > "dropped" together its corresponding temporary table > after a database session? I'm kind of surprised that it's possible to index a temporary table. There's not much point in doing so. Yes, the indexes would be dropped as well. -Josh Berkus ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster