On Thu, Jun 13, 2013 at 1:23 PM, k...@rice.edu <k...@rice.edu> wrote: > On Thu, Jun 13, 2013 at 12:58:18PM -0700, David Rees wrote: >> On Thu, Jun 13, 2013 at 12:13 PM, k...@rice.edu <k...@rice.edu> wrote: >> > We have it working here with dspam-3.10.2 and postgresql-9.2.4. >> >> Interesting - what OS are you running? I wonder if it may be because I >> don't have dspam linked against the same version of PostgreSQL. I have >> two systems, one a CentOS 6 system where dspam is linked against the >> OS provided pg libs (8.4) and another Fedora 17 system where dspam is >> linked against a self-compiled pg 9.0... >> >> Maybe I'll try recompiling dspam against pg 9.2 and see what happens... > > We are running on a RHEL 6.3 and using a locally built dspam to allow > access to some internal errors via STDERR that the current source does > not include. But I do not recall having any problems training with the > pre-built packages.
Weird. I just recompiled dspam against pg 9.2 on both affected systems and now training appears to work again. I can't believe that worked! Moral of the story - not a bad idea to link dspam against the same version of PostgreSQL that you are running! -Dave ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Dspam-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
