Re: BUG #1620: triggers breaks with alter table (at least with plpythonu)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Nahuel Greco" <ngreco(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1620: triggers breaks with alter table (at least with plpythonu)
Date: 2005-04-23 23:45:22
Message-ID: 23933.1114299922@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Nahuel Greco" <ngreco(at)gmail(dot)com> writes:
> If I create a trigger for a table, the trigger works
> ok, but if I add a new column to the table, then
> the trigger receives a NEW record with the old
> structure! I can fix that only if I remove the trigger
> from the table _and_ the trigger function.

Starting a fresh backend session would be sufficient. I believe the
issue is that plpython is caching tuple structure information.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message tesuji 2005-04-23 23:59:25 BUG #1622: not available
Previous Message Tom Lane 2005-04-23 23:41:21 Re: Transactions and "create or replace function"