Re: Re[4]: SPI_getvalue problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: gav <gav(at)nlr(dot)ru>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Re[4]: SPI_getvalue problem
Date: 2001-01-29 06:49:32
Message-ID: 20561.980750972@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alex Guryanow <gav(at)nlr(dot)ru> writes:
> DEBUG: tupdesc is NULL

Hm. Well, I can assure you that rd_att will *never* be null in a valid
relation cache entry. So there is something wrong with either
CurrentTriggerData, the relation pointer, or your function's
interpretation of the structures.

A thought that comes to mind here is that perhaps your function was
compiled against the wrong set of header files, causing it to think
that rd_att is at a different offset in the relation struct than what
the backend thinks. Do you have more than one version of Postgres
installed on the Solaris machine, and if so where are you picking up
the header files while building the library?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-01-29 06:57:29 Re: while vacuum: pq_flush: send() failed: Broken pipe
Previous Message Thomas T. Thai 2001-01-29 06:44:51 increase WAL_FILES