Re: Bug or Feature - plpgsql odity - Mailing list pgsql-general

From Tom Lane
Subject Re: Bug or Feature - plpgsql odity
Date
Msg-id 15114.1070253014@sss.pgh.pa.us
Whole thread Raw
In response to Re: Bug or Feature - plpgsql odity  ("Uwe C. Schroeder" <uwe@oss4u.com>)
List pgsql-general
"Uwe C. Schroeder" <uwe@oss4u.com> writes:
> On Sunday 30 November 2003 08:15 pm, Tom Lane wrote:
>> I see some fixes in the 7.4 CVS logs for dropped columns in plpgsql
>> rowtypes.  Not sure if they'd have any impact on added columns, but
>> you could try.  In general though I'd expect that plpgsql would cache
>> the definitions of rowtypes, the same as it does for tables.

> So how would I force a reload of the cache ?

Starting a fresh session would be sufficient.  If 7.4 doesn't do what
you want after starting a fresh session, please file a bug report with
details.

            regards, tom lane

pgsql-general by date:

Previous
From: "Uwe C. Schroeder"
Date:
Subject: Re: Bug or Feature - plpgsql odity
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Humor me: Postgresql vs. MySql (esp. licensing)