Re: BUG #14439: Trigger function fails with internal error after upgrade to 9.6

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: max(dot)valjanski(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14439: Trigger function fails with internal error after upgrade to 9.6
Date: 2016-11-29 15:26:24
Message-ID: 9452.1480433184@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

max(dot)valjanski(at)gmail(dot)com writes:
> Trigger function stopped working after upgrade from 9.5 to 9.6. Upgrade was
> performed via pg_upgrade.

After further thought I suspect this is the same issue discovered earlier
this month:

https://www.postgresql.org/message-id/flat/83shraampf.fsf%40is-it.eu

There's a patch here:

https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=f4d865f22

If you're not prepared to rebuild with the patch, I think the only
short-term workaround is to recreate the table without a dropped
column.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-11-29 16:19:13 Re: parallel sequential scan returns extraneous rows
Previous Message Tom Lane 2016-11-29 14:53:49 Re: BUG #14439: Trigger function fails with internal error after upgrade to 9.6