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,abstim
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
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> 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.
That isn't
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 un
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)?
--
Jim Nasby
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> And what two variants of errcontext drived by GUC? First current
> (compatible) and second enhanced (with oid, params, maybe all possible
debug
> values) and possible machine's readable. This enhanced variant can be
> compatible and shared in all
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> And what two variants of errcontext drived by GUC? First current
> (compatible) and second enhanced (with oid, params, maybe all possible debug
> values) and possible machine's readable. This enhanced variant can be
> compatible and shared in all env
Hi, Tom,
Tom Lane wrote:
>> I miss some info in context: function's oid, function's argumenst and
>> schema. Maybe:
>
>> 199292 function public.foo(int, int, int) language plpgsql statement
return
>> line 10
>
> Putting the OID there is a seriously awful idea, not least because it
> would make
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> I miss some info in context: function's oid, function's argumenst and
> schema. Maybe:
> 199292 function public.foo(int, int, int) language plpgsql statement
return
> line 10
Putting the OID there is a seriously awful idea, not least because it
wo
Hi, Tom,
Tom Lane wrote:
>> I miss some info in context: function's oid, function's argumenst and
>> schema. Maybe:
>
>> 199292 function public.foo(int, int, int) language plpgsql statement return
>> line 10
>
> Putting the OID there is a seriously awful idea, not least because it
> would mak
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> I miss some info in context: function's oid, function's argumenst and
> schema. Maybe:
> 199292 function public.foo(int, int, int) language plpgsql statement return
> line 10
Putting the OID there is a seriously awful idea, not least because it
woul
Hello,
I miss some info in context: function's oid, function's argumenst and
schema. Maybe:
199292 function public.foo(int, int, int) language plpgsql statement return
line 10
or short version:
1229298 function public.foo 10 return which is easy parseable
Best regards
Pavel Steh
12 matches
Mail list logo
