Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5R7XBa09632 for ; Wed, 27 Jun 2001 03:33:12 -0400 (EDT) (envelope-from dev@archonet.com) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 15F9pS-000CoR-0W; Wed, 27 Jun 2001 08:33:38 +0100 Received: from archonet.com (ibook.archonet.com [192.168.1.32]) by mainbox.archonet.com (Postfix) with ESMTP id 5141414562; Wed, 27 Jun 2001 08:19:50 +0100 (BST) Message-ID: <3B398892.D0001CDE@archonet.com> Date: Wed, 27 Jun 2001 08:17:38 +0100 From: Richard Huxton X-Mailer: Mozilla 4.7C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; I; PPC) X-Accept-Language: en MIME-Version: 1.0 To: Kristis Makris Cc: pgsql-sql@postgresql.org Subject: Re: Using the extract() function in plpgsql References: <200106202233.f5KMXSa91452@postgresql.org> <003701c0fa5e$722570a0$1001a8c0@archonet.com> <200106261958.f5QJwsa45412@postgresql.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200106/429 X-Sequence-Number: 3726 Kristis Makris wrote: > > Creating the temporary table first, and then inserting into it seems to > be a *somehow* functional workaround. However, the function cannot be > called again a second time during the same session, since the temporary > table already exists. Is there a way a table can be created truly > temporary, existing only within the scope of a plpgsql function? You could drop the temporary table at the end of the function, or do you need something more than that? - Richard Huxton