Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 48E609FB9CE for ; Wed, 17 Oct 2007 09:27:39 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 72024-08 for ; Wed, 17 Oct 2007 09:27:33 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from p15140235.pureserver.info (sql-info.de [217.160.166.164]) by postgresql.org (Postfix) with ESMTP id 8417B9FBB6F for ; Wed, 17 Oct 2007 09:27:33 -0300 (ADT) Received: by p15140235.pureserver.info (Postfix, from userid 639) id 653203B81; Wed, 17 Oct 2007 14:26:53 +0200 (CEST) Received: from iwate.sql-info.de (p54BE5CE3.dip.t-dialin.net [84.190.92.227]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by p15140235.pureserver.info (Postfix) with ESMTP id 345923B80; Wed, 17 Oct 2007 14:26:50 +0200 (CEST) From: Ian Barwick To: pgsql-docs@postgresql.org Subject: Re: FAQ corrections Date: Wed, 17 Oct 2007 14:27:49 +0200 User-Agent: KMail/1.9.5 Cc: Robert Treat , Bruce Momjian References: <200710161946.l9GJk6b06643@momjian.us> <200710161802.54084.xzilla@users.sourceforge.net> In-Reply-To: <200710161802.54084.xzilla@users.sourceforge.net> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_G/fFHaqrkUP3tjj" Message-Id: <200710171427.50421.barwick@gmx.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/63 X-Sequence-Number: 4484 --Boundary-00=_G/fFHaqrkUP3tjj Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wednesday 17 October 2007 00:02, Robert Treat wrote: > On Tuesday 16 October 2007 15:46, Bruce Momjian wrote: > > Robert Treat wrote: > > > On Friday 12 October 2007 14:04, Ian Barwick wrote: > > > > Hi > > > > > > > > attached some minor corrections, mainly completion of removal of > > > > the "relation with OID ##### does not exist" item, and some URL > > > > corrections. > > > > > > I'm curious why this was removed. We still get this question a bit on > > > irc and there aren't any more appropriate answers for any released > > > version than what the FAQ contained... > > > > The FAQ will match the release it goes with or we could just delay its > > removal until after 8.3 is in major circulation and say it only applies > > to pre-8.3. > > I think it should remain, with an addition that this problem should be > resolved as of PostgreSQL 8.3. Hard to say exactly when, but I would think > it would be at least untill 8.3 is released, and probably better would be 6 > months or so later, when (hopefully) people stop asking about this. IMHO. Sounds sensible. (I removed it while going through checking for broken links etc., and the section numbering didn't match the contents; checking against CVS it appeared the intention of Revision 1.393 was to remove this item, cf. http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ.html#rev1.393 ). Attached is an updated FAQ patch which re-includes this item and a note that it's been resolved in 8.3. Ian Barwick --Boundary-00=_G/fFHaqrkUP3tjj Content-Type: text/x-diff; charset="iso-8859-1"; name="FAQ.html.cdiff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="FAQ.html.cdiff" Index: FAQ.html =================================================================== RCS file: /projects/cvsroot/pgsql/doc/src/FAQ/FAQ.html,v retrieving revision 1.395 diff -r1.395 FAQ.html 117,118c117,121 < 4.19) What replication solutions are available?
< 4.20) Why are my table and column names not --- > 4.19) Why do I get "relation with OID ##### > does not exist" errors when accessing temporary tables in PL/PgSQL > functions?
> 4.20) What replication solutions are available?
> 4.21) Why are my table and column names no 1044c1047,1061 <

4.19) What replication solutions are available? --- >

4.19) Why do I get "relation with OID ##### > does not exist" errors when accessing temporary tables in PL/PgSQL > functions?

> >

PL/PgSQL caches function scripts, and an unfortunate side effect > is that if a PL/PgSQL function accesses a temporary table, and that > table is later dropped and recreated, and the function called again, > the function will fail because the cached function contents still > point to the old temporary table. The solution is to use > EXECUTE for temporary table access in PL/PgSQL. This > will cause the query to be reparsed every time.

> >

This problem has been resolved in PostgreSQL 8.3.

> >

4.20) What replication solutions are available? 1066c1083 <

4.20) Why are my table and column names not --- >

4.21) Why are my table and column names not --Boundary-00=_G/fFHaqrkUP3tjj--