Re: issues with dropped columns in plpgsql code again

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: issues with dropped columns in plpgsql code again
Date: 2013-05-10 20:17:46
Message-ID: 15412.1368217066@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> One user reported a issues with triggers related to dropped columns.
> When I checked his code, I found a more possible problems.

This is just the same kind of modified-rowtype problem we've discussed
before.

I continue to maintain that the only realistic fix is to stop using the
PLPGSQL_DTYPE_ROW infrastructure for variables of externally-defined
composite types. In the last go-round, this was rejected on the
(unproven) assumption that it would make things slower. But as a wise
man once said, you can make code arbitrarily fast if it doesn't have to
give the right answer.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2013-05-10 22:41:16 Re: corrupt pages detected by enabling checksums
Previous Message Andrew Dunstan 2013-05-10 20:12:06 Re: [patch] PSQLDIR not passed to pg_regress in contrib/pg_upgrade/test.sh