Re: inner join problem with temporary tables - Mailing list pgsql-general

From PFC
Subject Re: inner join problem with temporary tables
Date
Msg-id op.ttvsp1ircigqcu@apollo13
Whole thread Raw
In response to inner join problem with temporary tables  ("guillermo arias" <guillermoariast@linuxwaves.com>)
Responses Re: inner join problem with temporary tables
List pgsql-general
> This message appears:
>
> ERROR: relation "t_arti" does not exist
> SQL state: 42P01
> Context: SQL function "test1"
>
>
> Why it does not work???
> thanks for your help

    Because plpgsql functions are compiled on first execution and all queries
are then prepared. All tables are referenced directly in prepared
statements, not by name. Any prepared statement that refers to dropped
tables (even dropped temp tables) is thus unfit for consumption.

    This allows queries in plpgsql functions to be extremely fast, but it
isn't smart enough (yet) to recompile functions when a table the function
depends on is dropped.

    Just disconnect and reconnect, all prepared plans will be lost, and it
will work. Or issue your queries directly instead of using a function.

pgsql-general by date:

Previous
From: PFC
Date:
Subject: Re: pointer to feature comparisons, please
Next
From: Ron Johnson
Date:
Subject: Re: pointer to feature comparisons, please