Re: Re[4]: SPI_getvalue problem - Mailing list pgsql-general

From Tom Lane
Subject Re: Re[4]: SPI_getvalue problem
Date
Msg-id 20561.980750972@sss.pgh.pa.us
Whole thread Raw
In response to Re[4]: SPI_getvalue problem  (Alex Guryanow <gav@nlr.ru>)
Responses Re[6]: SPI_getvalue problem  (Alex Guryanow <gav@nlr.ru>)
List pgsql-general
Alex Guryanow <gav@nlr.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

pgsql-general by date:

Previous
From: "Thomas T. Thai"
Date:
Subject: Re: while vacuum: pq_flush: send() failed: Broken pipe
Next
From: "Thomas T. Thai"
Date:
Subject: Re: increase WAL_FILES