Re: issues with dropped columns in plpgsql code again

Dne 10.5.2013 22:17 "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal(a):
>
> 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.

Yes. It is same problém.

>
> 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.

Yes. It is probably solutions.

Regards

Pavel
>
> regards, tom lane