Jeff Trout <[EMAIL PROTECTED]> writes:
> it seems there may be some bug with cache coherency when replacing
> functions that use OUT arguments.
Looks like SysCacheGetAttr is making an assumption no longer tenable
(if it ever was), namely that the caller is referencing the same
syscache the tuple was fetched from, rather than another one on the
same catalog. It needs to be prepared to initialize the cache in case
this is the first reference. Will fix.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
