Re: [PATCH] GET DIAGNOSTICS FUNCTION_NAME

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] GET DIAGNOSTICS FUNCTION_NAME
Date: 2018-01-02 18:25:44
Message-ID: bbb44ce3-369b-586d-3206-185a358a2f99@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/31/17 11:57, Tom Lane wrote:
> 3. In connection with #2, I'm dubious that FUNCTION_NAME is le mot
> juste, because that would seem to imply that it is just the name,
> which it isn't. If we stick with the regprocedureout semantics
> I'd be inclined to propose FUNCTION_SIGNATURE.

The SQL standard has diagnostics items ROUTINE_CATALOG, ROUTINE_SCHEMA,
ROUTINE_NAME, which are used when there is an error invoking another
routine. Using notionally similar FUNCTION_* keys to mean my own
function seems pretty confusing (and also of questionable usefulness, as
you have commented).

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-01-02 18:45:17 Re: [HACKERS] SQL procedures
Previous Message Peter Eisentraut 2018-01-02 18:12:13 Re: AS OF queries