Re: segfault with contrib lo

On Mon, Oct 7, 2013 at 12:32 PM, Marc Cousin <cousinmarc@gmail.com> wrote:
> 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.

Thanks for the patch.  Please add it to the next CommitFest.

https://commitfest.postgresql.org/action/commitfest_view/open

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company