Group: pgsql.interfaces


Subject: request for more descriptive plperl error messages
From: tgl@sss.pgh.pa.us (Tom Lane)
Date: 10/5/2007 11:28:03 AM
Peter Eisentraut <peter_e@gmx.net> writes: > Am Mittwoch, 3. Oktober 2007 schrieb Robert Kleemann: >> ERROR:  error from Perl function: syntax error at or near "." at line 58. >> >> This is helpful to a degree but the critical missing information is the >> function name (schema name would be nice too). > You need to increase the error verbosity in psql, by running > \set VERBOSITY verbose Doesn't seem like that's going to provide the info he wants, namely the name of the plperl function that's being executed. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster

Subject: request for more descriptive plperl error messages
From: tgl@sss.pgh.pa.us (Tom Lane)
Date: 10/5/2007 3:15:03 PM
Robert Kleemann <kleemann@scharp.org> writes: > I'd like to modify the code to return the perl function name and submit > a patch but I've never developed in the postgres code base before and am > not sure where to start. Can the function and schema name be found in > the FunctionCallInfo structure that is passed? No. The easiest thing to do is save it in the plperl_proc_desc struct. See http://archives.postgresql.org/pgsql-committers/2007-10/msg00117.php regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster