paul at nfg
Jan 6, 2009, 2:36 PM
Post #10 of 11
(1483 views)
Permalink
|
My BSD wrote:
> On Tue, 06 Jan 2009 11:37:17 -0700
> Jesse Norell <jesse [at] kci> wrote:
>
> Hello Jesse and thank you!
>
>>> Tried to update the DB as follows:
>>>
>>> "# psql -U pgsql dbmail < 2_3_4-2_3_5.pgsql"
>>>
>>> With the following result:
>>> --------------------------------------------------------------------------------------------------------------------------------
>>> ALTER TABLE
>>> CREATE INDEX
>>> ALTER TABLE
>>> ERROR: syntax error at or near "VARCHAR"
>>> LINE 1: ALTER TABLE dbmail_users ALTER COLUMN passwd VARCHAR(130) NO...
>>> ^
>>> --------------------------------------------------------------------------------------------------------------------------------
>> That size was increased to handle some new hash types .. shouldn't be
>> a showstopper for you upgrading an existing system. It sounds like you
>> had another schema update problem too, though:
>>
>
> Lamentably, in my case it seems to be.
>
>>> The dbmail-imapd daemon started without incident, however, was not able to access
>>> the existing account from KMail.
>>>
>>> Log entries follow:
>>> --------------------------------------------------------------------------------------------------------------------------------
>>> Jan 06 11:08:43 [server name] dbmail-imapd[55335]: [0x2881e820] Error: [db]
>>> db_getmailbox_mtime(+2472): SQLException: ERROR: column "mtime" does not
>>> exist LINE 1: SELECT name,ROUND(DATE_PART('epoch',mtime)) FROM
>>> dbmail_mail...
>>> --------------------------------------------------------------------------------------------------------------------------------
>> As that says, it's trying to use a column named "mtime" which doesn't
>> exist in your schema. If the migration scripts are broken or there was
>> an old update you missed or something, you may have to add that
>> manually.
>>
>
> How would that be done (for the Postgresql ignorant)?
>
>>> Created new database and tried to apply update with the following result:
>>> --------------------------------------------------------------------------------------------------------------------------------
>>> # psql -U pgsql dbmail-2.3.5 < /usr/local/share/dbmail/postgresql/2_3_4-2_3_5.pgsql
>>> ERROR: column "seq" of relation "dbmail_mailboxes" already exists
>>> ERROR: relation "dbmail_mailboxes_seq" already exists
>>> ERROR: column "mtime" of relation "dbmail_mailboxes" does not exist
>>> ERROR: syntax error at or near "VARCHAR"
>>> LINE 1: ALTER TABLE dbmail_users ALTER COLUMN passwd VARCHAR(130) NO...
>>> ^
>>> --------------------------------------------------------------------------------------------------------------------------------
>> If indeed you're creating a new database here, use the full 2.3.5
>> schema directly, don't put in and old version and update it (though by
>> right you should end up with the same thing in either case if everything
>> works right).
>>
>
> I could not find the schema in the 2.3.5 tarball. In fact, the "create_tables.pgsql" file
> included with 2.3.5 is the same as the one included with 2.3.5:
Yes, as 1 equals 1. The create_tables.XXXX files are meant to be the
current schema.
>
> ---------------------------------------------------------------------------------------
> # diff create_tables.pgsql-2.3.4 create_tables.pgsql-2.3.5
Wrong. You are mixing trees here.
git diff v2.3.4..v2.3.5 sql/postgresql/create_tables.pgsql
and you can track the changes involved using:
git-format-patch --stdout v2.3.4..v2.3.5 \
sql/postgresql/create_tables.pgsql
--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
https://mailman.fastxs.nl/mailman/listinfo/dbmail
|
signature.asc
