| From: | Jim Nasby <jimn(at)enterprisedb(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)hotmail(dot)com> |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PL/pgSQL Todo, better information in errcontext from plpgsql |
| Date: | 2006-10-06 15:35:01 |
| Message-ID: | 7EB498DD-B199-48FD-8B98-C626CD4F82D8@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)enterprisedb(dot)com
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-10-06 15:54:51 | Re: pg_dump exclusion switches and functions/types |
| Previous Message | Graham Davis | 2006-10-06 15:05:04 | Re: [HACKERS] timestamp subtraction (was Re: formatting intervals |