|From:||Marc Cousin <cousinmarc(at)gmail(dot)com>|
|To:||'PostgreSQL Hackers' <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||segfault with contrib lo|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
I was using the lo contrib a few days ago and wasn't paying attention, and
forgot the "for each row" in the create trigger command... PostgreSQL
segfaulted, when the trigger tried to access the row's attributes.
Please find attached a patch to control that the trigger is correctly defined
(as in the example): a before trigger, for each row, and a parameter (if the
parameter was omitted, it segfaulted too). I hope I did this correctly.
|Next Message||Robert Haas||2013-10-07 17:25:17||Re: space reserved for WAL record does not match what was written: panic on windows|
|Previous Message||David Fetter||2013-10-07 15:43:27||Re: old warning in docs|