Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e7O5Wr519315 for ; Thu, 24 Aug 2000 01:32:53 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id BAA25718; Thu, 24 Aug 2000 01:32:45 -0400 (EDT) To: "Hiroshi Inoue" cc: "Andreas Tille" , "PostgreSQL SQL" Subject: Re: Create table in functions In-reply-to: <000201c00d66$3953ea80$2801007e@tpf.co.jp> References: <000201c00d66$3953ea80$2801007e@tpf.co.jp> Comments: In-reply-to "Hiroshi Inoue" message dated "Thu, 24 Aug 2000 09:57:06 +0900" Date: Thu, 24 Aug 2000 01:32:45 -0400 Message-ID: <25715.967095165@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200008/259 "Hiroshi Inoue" writes: > Hmm,Andreas's original function seems to contain other statements. > If the function contains DML statements for the table Temp_Num_Table, > it wouldn't work properly. i.e 1st call would work but 2nd call woudn't. Are you thinking about plpgsql's caching of query plans (and specifically the table OIDs stored in those plans) or is there another issue here? We do need to think about invalidating cached query plans when updates happen... regards, tom lane