From: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
---|---|
To: | Thomas Hallgren <thhal(at)mailblocks(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: OID of current function |
Date: | 2005-01-12 15:44:11 |
Message-ID: | 20050112154411.GZ67721@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jan 12, 2005 at 04:08:28PM +0100, Thomas Hallgren wrote:
> Jim C. Nasby wrote:
> >Is there an easy way to get the OID of the currently running function?
> >(IE: the function you're in when you execute the code to see what
> >function you're in, if that makes any sense).
>
> In what language? In C you can use:
>
> Datum your_function(PG_FUNCTION_ARGS)
> {
> Oid funcOid = fcinfo->flinfo->fn_oid;
> ...
> }
This would be in plpgsql.
Some other info:
What I'm trying to do is use contrib/userlock to serialize access to a
function. The only effective way to come up with a unique lock number
that I've been able to think of is to use the OID of the function
itself.
What I find somewhat interesting is every other database I've used that
exposes some kind of 'object ID' has a set of functions to map between
an object name and it's ID, and vice-versa. It seems like this is
something that would be good for PostgreSQL to have.
--
Jim C. Nasby, Database Consultant decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
From | Date | Subject | |
---|---|---|---|
Next Message | bsimon | 2005-01-12 16:15:57 | Debugging SPI C functions |
Previous Message | Tom Lane | 2005-01-12 15:14:51 | Re: Bug in pg_dump in 7.4.6? |