Re: plan invalidation vs stored procedures - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plan invalidation vs stored procedures
Date
Msg-id 4793.1217944277@sss.pgh.pa.us
Whole thread Raw
In response to Re: plan invalidation vs stored procedures  (Martin Pihlak <martin.pihlak@gmail.com>)
Responses Re: plan invalidation vs stored procedures  ("Asko Oja" <ascoja@gmail.com>)
Re: plan invalidation vs stored procedures  (Martin Pihlak <martin.pihlak@gmail.com>)
List pgsql-hackers
Martin Pihlak <martin.pihlak@gmail.com> writes:
> create function foo() returns integer as $$ begin return 1; end; $$ language plpgsql;
> CREATE FUNCTION
> prepare c1 as select * from foo();
> PREPARE
> execute c1;
>  foo
> -----
>    1
> (1 row)

> drop function foo();
> DROP FUNCTION
> create function foo() returns integer as $$ begin return 2; end; $$ language plpgsql;
> CREATE FUNCTION
> execute c1;
> psql:test.sql:11: ERROR:  cache lookup failed for function 36555

This is simply a bad, wrong, stupid way to do it.  Why do you not use
CREATE OR REPLACE FUNCTION?
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: IN vs EXISTS equivalence
Next
From: Markus Wanner
Date:
Subject: Re: Automatic Client Failover