pgsql: Defend against bad trigger definitions in contrib/lo's lo_manage

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Defend against bad trigger definitions in contrib/lo's lo_manage
Date: 2013-11-24 03:47:00
Message-ID: E1VkQey-0004CN-5w@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Defend against bad trigger definitions in contrib/lo's lo_manage() trigger.

This function formerly crashed if called as a statement-level trigger,
or if a column-name argument wasn't given.

In passing, add the trigger name to all error messages from the function.
(None of them are expected cases, so this shouldn't pose any compatibility
risk.)

Marc Cousin, reviewed by Sawada Masahiko

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/64d15e424091d8fd2c882356ee4bf07cfc5ff69d

Modified Files
--------------
contrib/lo/lo.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Meskes 2013-11-24 11:27:42 pgsql: Distinguish between C and SQL mode for C-style comments.
Previous Message Peter Eisentraut 2013-11-24 02:34:59 pgsql: PL/Tcl: Add event trigger support