"Rod Taylor" <rod(dot)taylor(at)inquent(dot)com> writes:
> Is there any easy method for getting a hold of the OID and XID for a
> given row within a plpgsql (or another type) of function?
> Statements like NEW.oid appear to fail, and xid isn't to be found.
The reason this doesn't work in plpgsql is that the underlying "SPI"
tuple-access routines don't support access to the system attributes
of a tuple. It'd be relatively straightforward to extend them to
do so, if someone cared to work on that.
I thought you could do it in an SQL-language function, but that doesn't
seem to work either, for reasons that may be strictly historical at
this point --- the relevant error message is coming out of this:
attno = get_attnum(relid, attname);
/* XXX Is there still a reason for this restriction? */
if (attno < 0)
elog(ERROR, "Cannot reference attribute '%s'"
" of tuple params/return values for functions", attname);
Think I'll look and see if this restriction could be dropped now.
For 7.0.* though, it seems the only way to get this data in a PL
function is to write a C-language function to extract it ...
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2001-01-23 02:00:25|
|Subject: Re: int4 or int32 |
|Previous:||From: Tatsuo Ishii||Date: 2001-01-23 01:54:53|
|Subject: Re: AW: like and optimization|