Re: access to Bayes in PostgreSQL DB broken
Hi Mikael, Have you looked in the sql for postgres ? Have the structure changed? I have compared the latest dump of my spamassassin database with the ddl scripts provided by spamassasin. There really were some changes. For example the table bayes_token now uses bytea instead of character(5). I have recreated the database structure and imported the previous data. One entry couldn't be imported, but the others worked fine. And bayes is running again! Thanks for the hint. Regards Marco
Re: access to Bayes in PostgreSQL DB broken
Hi Martin, On Thu, 2010-04-08 at 20:43 +0200, m...@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. [..] Its highly likely that Postgres 8.3.9 can't read a database created by 7.4.x. You'll need to recreate the database with 8.3.9 and restore the latest backup. See 24.5. Migration Between Releases in the Postgres manual for more details. I already restored the latest backup of the database. The problem was, that I didn't recreate the tables. These seem to have changed. After recreating them and importing the data again, it works. Thanks for your help. Marco
access to Bayes in PostgreSQL DB broken
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
Re: access to Bayes in PostgreSQL DB broken
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, m...@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
