Package: spamassassin
Version: 3.1.0a-1
Severity: normal

 I am trying to upgrade to spamassassin 3.1 and wanted to convert
 our bayes database from the old Berkeley database to use
 our Postgres installation that works for other packages. I 
 followed the bayes readme and the bayes.pg readme
 and created a spamassassin postgres database to use.
 I then tried 
 psql -U postgres -f bayes_pg.sql spamassassin and 
 partway through the program I get an error message.
 Here is the total output from the program.


psql:bayes_pg.sql:13: NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit 
index "bayes_global_vars_pkey" for table "bayes_global_vars"
psql:bayes_pg.sql:22: NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit 
index "bayes_seen_pkey" for table "bayes_seen"
psql:bayes_pg.sql:31: NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit 
index "bayes_token_pkey" for table "bayes_token"
psql:bayes_pg.sql:47: NOTICE:  CREATE TABLE will create implicit sequence 
"bayes_vars_id_seq" for "serial" column "bayes_vars.id"
psql:bayes_pg.sql:47: NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit 
index "bayes_vars_pkey" for table "bayes_vars"
psql:bayes_pg.sql:112: ERROR:  syntax error at or near "INTEGER" at character 48

THe error appears to come from the plpgsql procedure that is defined,
but I don't know enough about the language to see anything obvious.

I am running SA fine by still using our old BDB bayes database but it
would be great if I can get it transferred to our Postrgres.


 -- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.25.050304.03smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages spamassassin depends on:
ii  libdigest-sha1-perl           2.10-1     NIST SHA-1 message digest algorith
ii  libhtml-parser-perl           3.45-2     A collection of modules that parse
ii  perl                          5.8.4-8    Larry Wall's Practical Extraction 

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to