| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Uwe C(dot) Schroeder" <uwe(at)oss4u(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Bug or Feature - plpgsql odity |
| Date: | 2003-12-01 04:30:14 |
| Message-ID: | 15114.1070253014@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Uwe C. Schroeder" <uwe(at)oss4u(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2003-12-01 04:39:45 | Re: Humor me: Postgresql vs. MySql (esp. licensing) |
| Previous Message | Uwe C. Schroeder | 2003-12-01 04:24:03 | Re: Bug or Feature - plpgsql odity |