Re: access to Bayes in PostgreSQL DB broken

[Mikael Syska <mi...@syska.dk>]

Hi,

Have you looked in the sql for postgres ? Have the structure changed?

That would be my first step to make sure. ( I'm using InnoDB MySQL )
and between 3.2.5 and 3.1.1 only some Indexes changed ... but I can
see you come from a very very old version I think.

mvh

On Thu, Apr 8, 2010 at 8:43 PM,  <ml...@mherrn.de> wrote:
> Hi,
>
> I am running spamassassin with a PostgreSQL DB as bayes storage.
> After an upgrade from debian etch to debian lenny, this bayes storage
> doesn't work anymore.
> The following error appears in the logfile when debugging of bayes related
> actions is switched on:
>
> Thu Apr  8 19:57:19 2010 [15631] dbg: bayes: tok_get_all: SQL error:
> ERROR: operator does not exist: character = bytea
> Thu Apr  8 19:57:19 2010 [15631] dbg: bayes: LINE 4: AND token IN
> ($2,$3,$4,$5,$6,$7,$8,$9,...
> Thu Apr  8 19:57:19 2010 [15631] dbg: bayes: ^
> Thu Apr  8 19:57:19 2010 [15631] dbg: bayes: HINT: No operator matches the
> given name and argument type(s). You might need to add explicit type
> casts.
>
> The version of spamassassin I am running now is 3.2.5, postgres is 8.3.9. I
> am not absolutely sure, but I think the version of postgres prior to the
> upgrade was 7.4 and the version of spamassassin 3.1.7.
>
> Not it seems that I need to upgrade the database in some way. But the docs
> didn't give any hints.
>
> Some ideas?
> Regards Marco
>
>
>
>