X-Original-To: pgsql-sql@postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by developer.postgresql.org (Postfix) with ESMTP id 2C040925137 for ; Wed, 28 May 2003 20:18:23 -0400 (EDT) Received: from developer.postgresql.org ([64.117.224.193]) by localhost (developer.postgresql.org [64.117.224.193:10024]) (amavisd-new) with ESMTP id 75976-10 for ; Wed, 28 May 2003 20:18:22 -0400 (EDT) Received: from mail2.tpgi.com.au (mail.tpgi.com.au [203.12.160.58]) by developer.postgresql.org (Postfix) with ESMTP id 73A76925063 for ; Wed, 28 May 2003 20:18:21 -0400 (EDT) Received: from jac (203-219-31-196-bri-ts8-2600.tpgi.com.au [203.219.31.196]) by mail2.tpgi.com.au (8.12.9/8.12.9) with SMTP id h4T0HxLf029872 for ; Thu, 29 May 2003 10:18:01 +1000 Message-ID: <001a01c32577$ccee2180$1400a8c0@jac> From: "jack" To: Subject: The problems about temporary tables in V7.3.2 Date: Thu, 29 May 2003 10:17:56 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Kaspersky-Antivirus: Passed X-Virus-Scanned: by amavisd-new X-Archive-Number: 200305/543 X-Sequence-Number: 13708 Hi All A view is created with a normal table xx without a schema specified. And before using the view, a temporary table xx , which has the same name as the normal table xx used by the view. In the same connection session, it supposes the view would read the temporary table. But actually it always reads the normal table instead of temporary table. The same thing happens to the table specified with a schema. If a SELECT statement uses a table with a schema specified, the SELECT statement won't read the temporary table when it exists with the same name. I just wonder the schema feature just removes the access priority of the temporary tables. Jack