> Hi Ken, > Hallo Tom,
> Many thanks for your reply. What would be the implication of losing the > dspam_signature_data? > After loosing the data in dspam_signature_data users will not be able to retrain mails since you have purged the signatures. But any new mail getting processed by DSPAM after the purging will work. > I'm quite happy to write a perl script to move the data from Mysql to > Postgres and it doesn't sound too complicated. > > Can you point me in the direction of the recent posts re perfomrance > tips in DSPAM with Postgres 8.3? I can't seem to find them... > > Best Regards, > Tom > Steve > -- > > On 06/25/09 13:49, Kenneth Marshall wrote: > > Hi Tom, > > > > We are looking at that same transition this summer. I have already > > spent a little time looking at what will be needed to migrate from > > MySQL to PostgreSQL. The two tables that are most critical are the > > dspam_token_data and dspam_signature_data. But with a teeny bit of > > cooperation/warning to your users, you can just start from scratch > > with the signature data since it expires after a week or so anyway. > > > > You can use a perl script to move the data from MySQL to PostgreSQL. > > The key is to offset the data in PostgreSQL since it does not have > > an unsigned bigint type. One easy way is to define the type as > > NUMERIC(20) as it was in early releases. Dump the data from MySQL > > to PostgreSQL using COPY and then run the program dspam_pg2int8.c > > from tools.pgsql_drv to convert it to BIGINT. > > > > You can migrate the signature data as well, but I have not had a > > chance to generate the perl script to do that. We should have it > > by the end of the summer. Please see some of the recent posts > > concerning performance tips in DSPAM with PostgreSQL 8.3+. > > > > Regards, > > Ken > > > > On Thu, Jun 25, 2009 at 12:54:30PM +0100, Tom Robst wrote: > >> Hi Steve, > >> > >> Thanks for the info regarding the UPGRADING document. That is very > >> useful. Ideally I would like to move from MySQL to PostgreSQL since > this > >> is our main database engine for other applications too. What is > >> performance like on Postgres now since I seem to remember that it was > >> quite a lot slower than MySQL in the early days? Is there a simple > >> method to migrate user data from MySQL to Postgres? > >> > >> Best Regards, > >> Tom > >> -- > >> > >> On 06/25/09 09:23, Tom Robst wrote: > >>> Hi, > >>> > >>> Good news to hear the DSPAM project is alive and well and a new > release > >>> is out! Thank you for all your hard work. > >>> > >>> I've been using DSPAM for a long time and it's been a while since I > last > >>> updated. I'm currently using version 3.6.8 - is updating > straightforward > >>> to the 3.9.0 release? I'm using MySQL on Linux as the storage and > >>> filtering through Postfix. > >>> > >>> Kind Regards, > >>> Tom > >> > ------------------------------------------------------------------------------ > >> _______________________________________________ > >> Dspam-user mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/dspam-user > >> > > > > !DSPAM:4,4a437561240751067614841! > > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Dspam-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspam-user -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ------------------------------------------------------------------------------ _______________________________________________ Dspam-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspam-user
