From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: question about fixes in v7.4... |
Date: | 2003-11-20 13:52:06 |
Message-ID: | 1069336326.10335.10728.camel@camel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2003-11-19 at 22:50, Bruce Momjian wrote:
> Don Sceifers wrote:
> > My company is fairly new at Postgresql, but we have hit a problem, where
> > we modify a table using ALTER, and our stored procedures stop working. We
> > have a grasp as to why this happens, but I was wondering if this v7.4
> > upgrade fixes this issue?
>
> This is a known issue. There is no way for us to know what stored
> tables/columns you are using in your function. You might find that
> reconnecting to the database after the ALTER will fix the problem. We
> do cache function code, so reconnecting will erase that cache.
>
Would it be worth putting in a partial implementation? I'm thinking
specifically about functions that return table types. Could they be
hooked up with dependency information and made to complain?
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2003-11-20 14:10:22 | Re: ALTER COLUMN/logical column position |
Previous Message | Rod Taylor | 2003-11-20 13:34:19 | Re: 4 Clause license? |