Re: BUG #14406: Statement fails after upgrade to 9.6.1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: boskowski+coreybernal(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14406: Statement fails after upgrade to 9.6.1
Date: 2016-10-31 15:58:31
Message-ID: 18457.1477929511@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

boskowski+coreybernal(at)gmail(dot)com writes:
> After upgrading from 9.5.4 to 9.6.1 using pg_upgrade with links an UPDATE
> (prepared) statement that previously worked started raising

> ERROR: table row type and query-specified row type do not match
> DETAIL: Query provides a value for a dropped column at ordinal position
> 19.

> I managed to solve this by creating an identical table, populating with
> INSERT/SELECT and swapping the tables by renaming them, all in one
> transaction.

> Please let me know what detail information can be helpful to you.

Without a self-contained test case, we're not going to be able to do much
with this report. Presumably a test case would look something like
"create a table like this under 9.5; drop some columns in it like this;
pg_upgrade to 9.6; execute this query". But nobody's going to try to
fill in all those details by guessing.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2016-10-31 16:55:38 Re: BUG #14397: Updatable VIEW doesn't work with ON CONFLICT from PgPreparedStatement
Previous Message boskowski+coreybernal 2016-10-31 12:42:40 BUG #14406: Statement fails after upgrade to 9.6.1