That would be good news. I started with 2.0.10 only a couple months
ago, but looking at the create table script for that version they are
just text.
So you are saying that during the messageblk switch to bytea, no inserts
are going to happen anyway? So I could just take down lmtpd and leave
pop3 and imap running?
Aaron Stone wrote:
The operations that require write locks on the main storage tables are at
the very top of the migrate_from_2.0_to_2.2.pgsql script. It's the block
of SQL that recasts the messageblks as bytea instead of text. Depending on
when you started using DBMail, you might already have bytea messageblks,
and you'll be able to drop this portion of the upgrade script.
The remaining sections only add columns and new tables. Nothing is renamed
or removed. I believe that it can safely run on a live table.
Once the tables schemas are updated, you can take down your DBMail 2.0
processes and spin up DBMail 2.2. You then need to run dbmail-util -ay to
populate the cache tables. I believe that you can safely do this while
DBMail 2.2 is running; new messages will have their cache entries fully
inserted, and old messages will run in a degraded mode.
Aaron
