Received: from megazone.bigpanda.com ([63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fAS0W0m24999 for ; Tue, 27 Nov 2001 19:32:00 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 24EC7D5E9; Tue, 27 Nov 2001 16:32:03 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 188A95BEB; Tue, 27 Nov 2001 16:32:03 -0800 (PST) Date: Tue, 27 Nov 2001 16:32:03 -0800 (PST) From: Stephan Szabo To: Josh Berkus Cc: Aasmund Midttun Godal , Subject: Re: PL/pgSQL examples NOT involving functions In-Reply-To: Message-ID: <20011127162754.I23668-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200111/373 X-Sequence-Number: 5755 On Tue, 27 Nov 2001, Josh Berkus wrote: > Aasmund, > > > envisity=# DROP TABLE temp ; > > DROP > > envisity=# create table temp (tempid integer); > > CREATE > > envisity=# INSERT INTO temp VALUES(3); > > INSERT 150371 1 > > envisity=# select test3(); > > ERROR: Relation 150348 does not exist > > envisity=# > > That's a new one on me. I've dropped and re-created dozens of tables, > and while I have to re-build the views, I've never had to touch the > functions for that reason. Either in PL/pgSQL or in SQL. > > What version are we talking about? 7.2b3 :) One thing that should be noted here is that after reconnecting you should get the 3 back out. IIRC parse tree stuff is done first time its called through a connection. So, if you're dropping and doing stuff via like editing files and psqling them and then starting a psql and trying your function you won't see it happen.