Quassel IRC

Hi,

I am having zero success migrating an existing SQLite backend core to PostgreSQL using 0.5rc1.

I asked about this on #quassel earlier today, but while I was able to get quassel working via postgres in the end by starting from scratch, I figured it would be a good idea to report the unresolved migration issue, especially since I have now encountered the problem twice on two completely different systems.

The first was an Ubuntu Server system running a pretty fresh 9.2 Jaunty install. This had little history in the existing SQLIte backend so I didn't mind having to completely start from scratch.
The second was a gentoo system. This has quite a bit of history that I really want to be able to migrate.

Both a running Postgres 8.3 with pretty much stock configurations (no tuning yet).

In both cases I followed the instructions on the wiki: PostgreSQL.

In both cases, the first time I tried the migration it told me that the existing backend did not support migration and so did not attempt to. It created the tables in the database correctly, but did not attempt to populate any data other than coreinfo.

When starting up the core, the log just showed that it was using the SQLite backend and did not mention the Postgres one all all.

I had more success by explicitly configuring the core to the SQLite backend before attempting the conversion. In this case, migration was attempted and output was given stating that migration was taking place for each of the tables. However, this was suspiciously fast, given that one of my two machines has quite a bit of data to migrate, and sure enough there was no data in the database post-migration. And again, when starting up the core, the SQLite backend was used just as before.

For a bit of further debugging, I configured postgres to output statements when performing the migration. What I found was that while insert queries were being prepared, none were being executed. This would explain the speed at which the migration took place, and the lack of data in the new database.

It would appear that there are potentially two things wrong here:

1. The new backend is not being correctly configured, which results in the core ignoring it when starting up. This could extend to quassel's configuration itself not being updated to reflect postgresql as being the current backend
 2. The migration process does not appear to be reading any data from the sqlite database to insert into the new backend.

Given that I have encountered the same problem on two separate systems from different distros, this should be reproducable. :) However, knowing my luck nobody else will be able to get behaviour even remotely similar to what I'm experiencing. However, it's worth a try.