Re: BUG #15203: trigger does not recognize schema changes when passing on data

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
Cc: easteregg(at)verfriemelt(dot)org, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15203: trigger does not recognize schema changes when passing on data
Date: 2018-05-18 14:13:46
Message-ID: 27908.1526652826@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> writes:
> On Fri, May 18, 2018 at 4:48 PM, <easteregg(at)verfriemelt(dot)org> wrote:
>> b) shouldnt the function become aware of the change defintion of its
>> parameter type?

> It should. But I am not sure why it is not getting latest definition.
> I am not able to reproduce this issue in the development version (11 devel).

Since the OP hasn't shown us exactly what he did to get into this
situation, it's hard to be sure, but I think we fixed this for v11.
At least, v11 makes a reasonable attempt to cope with during-a-session
changes in the rowtypes of named-composite-type variables, which no
prior version did.

> I am not sure whether it can be backported to fix this issue?

Zero chance of that --- it was a large set of changes.

> d) can i manually reload the internal functions?

> I doubt that there is any way to manually reload the functions.

I think a no-op ALTER FUNCTION might be enough, but reconnecting
is probably an easier answer.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dave Cramer 2018-05-18 14:23:46 Re: JDBC problem in 10.3 / 10.4
Previous Message Huong Dangminh 2018-05-18 12:40:33 RE: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT