| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Marc Cousin <cousinmarc(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: segfault with contrib lo |
| Date: | 2013-10-08 16:28:46 |
| Message-ID: | CA+TgmoZxg9M68abs-Fst5q76b+RtBxbD2TZsoE7zNWmAWbRapA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 7, 2013 at 12:32 PM, Marc Cousin <cousinmarc(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-10-08 16:30:43 | Re: Patch: FORCE_NULL option for copy COPY in CSV mode |
| Previous Message | Robert Haas | 2013-10-08 16:27:08 | Re: old warning in docs |