[Users] postgres and long AVPs values BUG?

Reposting, since it seems it's didn't reach the list. JF ---------- Forwarded message ---------- From: JF &lt;jfkavaka(a)gmail.com&gt; Date: Jan 27, 2006 5:28 PM Subject: postgres and long AVPs values BUG? To: users(a)openser.org Hi, I increased the length of the value column in the usr_preferences table from 128 to 1024, but I got a core dump after these logs: 0(24138) val2str(): converting record_route, 12 0(24138) PG[224] str2valp got string <sip:10.112.64.59;ftag=605ff764c617d3cd28dbbdd72be8f9a2;lr=on>,<sip:10.112.64.12;ftag=605ff764c617d3cd28dbbdd72be8f9a2;lr=on>,<sip:10.112.64.12;ftag=605ff764c617d3cd28dbbdd72be8f9a2;lr=on>,<sip:10.112.64.59;ftag=605ff764c617d3cd28dbbdd72be8f9a2;lr=on> Segmentation fault (core dumped) This was caused by an avp_db_load() call from the script. I'm using OpenSER 1.0.0. I found the following comment on modules/postgres/db_res.c that might have something to do with it: /* I'm not sure about this */ /* PQfsize() gives us the native length in the database, so */ /* an int would be 4, not the strlen of the value */ /* however, strlen of the value would be easy to strlen() */ Also, in modules/postgres/db_val.c, there is a FIXME in val2str() function that seems to be related. Can anyone help solve this problem? It seems like a bug. Thanks, JF