On Sun, Jun 13, 2010 at 7:20 PM, Maxim Boguk wrote:
> I think changes in 9.0 now mask actual bug instead of fix it. If I was
> wrong, still would be useful to know how to use return record from
> trigger function in that case, because I can't make a working version
> at all.
Why do you think that
HI all.
Look like no one think this behavior is bug.
Then need change documentation probably, because in
http://www.postgresql.org/docs/8.4/interactive/plpgsql-trigger.html
specified:
"To alter the row to be stored, it is possible to replace single
values directly in NEW and return the modified NE
I see... but anyway this bug does not allow use return record value
from a trigger in table contained at least one dropped column, and
even worse trigger will work on fresh loaded copy of production
database and would pass all possible tests, but on production database
it is stop working. Moreover,
"Maksym Boguk" writes:
> This bug hard to describe. But in general if a table contained dropped
> columns you cannot use return record variable in trigger function.
This is fixed for 9.0 ... or at least the specific test case you provide
doesn't fail. We have not risked back-porting the change t
The following bug has been logged online:
Bug reference: 5503
Logged by: Maksym Boguk
Email address: maxim.bo...@gmail.com
PostgreSQL version: 8.4.3
Operating system: Linux 2.6.18-164
Description:error in trigger function with dropped columns
Details:
This bug hard
