Re: Re[4]: SPI_getvalue problem
От | Tom Lane |
---|---|
Тема | Re: Re[4]: SPI_getvalue problem |
Дата | |
Msg-id | 20561.980750972@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re[4]: SPI_getvalue problem (Alex Guryanow <gav@nlr.ru>) |
Ответы |
Re[6]: SPI_getvalue problem
|
Список | 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 по дате отправления: