Re: PL/pgSQL Todo, better information in errcontext from plpgsql - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: PL/pgSQL Todo, better information in errcontext from plpgsql
Date
Msg-id 7EB498DD-B199-48FD-8B98-C626CD4F82D8@enterprisedb.com
Whole thread Raw
In response to Re: PL/pgSQL Todo, better information in errcontext from plpgsql  ("Pavel Stehule" <pavel.stehule@hotmail.com>)
Responses Re: PL/pgSQL Todo, better information in errcontext from plpgsql  ("Pavel Stehule" <pavel.stehule@hotmail.com>)
List pgsql-hackers
On Oct 6, 2006, at 1:47 AM, Pavel Stehule wrote:
>> On Oct 5, 2006, at 9:30 AM, Pavel Stehule wrote:
>>> With func oid I can get all other info later, without it, I need   
>>> estimate which functions are in stack track.
>>
>> Why do you need the OID to know exactly what function something  
>> is?  What's wrong with schema.function(args)?
>> --
>
> oid is simply unique. I can take source code, args and all without  
> parsing. It's only one difference. I unlike parsing.

decibel=# select 'pg_catalog.abstimelt 
(abstime,abstime)'::regprocedure::oid;
oid
-----
253

--
Jim Nasby                                    jimn@enterprisedb.com
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)




pgsql-hackers by date:

Previous
From: Graham Davis
Date:
Subject: Re: timestamp subtraction (was Re: [SQL] formatting intervals
Next
From: Tom Lane
Date:
Subject: Re: pg_dump exclusion switches and functions/types