On Friday 18 March 2005 14:29, Stephan Szabo wrote:
> Given the error message, this seems to be the whole plpgsql caches query
> plans but we don't invalidate those plans when there are schema changes.
I already tried to execute the 'CREATE TEMP TABLE' statement using EXECUTE to
avoid cache probl
> "Roy" == Roy Badami <[EMAIL PROTECTED]> writes:
Roy> FWIW, this is documented behaviour (section 35.1 of the
Roy> manual).
That's 35.1 in the 8.0 doc, BTW. It's 37.1 in the 7.4 doc.
Roy> -roy
---(end of broadcast)---
TIP
> Given the error message, this seems to be the whole plpgsql caches
> query plans but we don't invalidate those plans when there are schema
> changes. In all currently released versions you pretty much need to
> use EXECUTE on any queries where the table may go away, for example,
> any use of te
On Fri, 18 Mar 2005, Oliver Siegmar wrote:
> On Friday 18 March 2005 14:29, Stephan Szabo wrote:
> > Given the error message, this seems to be the whole plpgsql caches query
> > plans but we don't invalidate those plans when there are schema changes.
>
> I already tried to execute the 'CREATE TEM
On Tue, 15 Mar 2005, Oliver Siegmar wrote:
> Here's a demonstration of the bug:
>
> CREATE FUNCTION testfunction()
> RETURNS void
> AS '
> BEGIN
> CREATE TEMP TABLE testtable (field int4) ON COMMIT DROP;
>
> INSERT INTO testtable (field) VALUES (1);
>
> -- DROP TABLE te
The following bug has been logged online:
Bug reference: 1546
Logged by: Oliver Siegmar
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7 / 8.0.1
Operating system: Linux x86
Description:Temp table isn't deleted at the end of a transaction /
ON COMMIT DROP has
