* Hans Scheffers
I think in the update scripts for postgres there is an error. Twice there is a column added with attribute 'NOT NULL'. This isn't allowed in postgres, first you have to add the column and after that you should alter it with ' alter table alter column set not null'
(I've been bitten by this as well.) On the topic of Postgres, might I also suggest ditching the bigint and serial8-types in favour of more conventional int and serial-types? As it is, OTRS is producing queries that don't take advantage of indexes. I've seen this noticeably affect performace with no more than 5-10k tickets and 20-30k articles. Literal integers default to int4 in Postgres, and because of this conditions like "... where foo = 42" will result in a sequential scan instead of an index lookup if foo is bigint. Even if foo is indexed. Alternately, this could be fixed by explicitly casting all literal integers used in comparisons with bigint-attributes to bigint. This would probably be less than compatible, and seriously, who needs 64 bits of article space anyway? 32 bits, even signed, will let you enter one article every second 24/7 for 34 years. (And by the time you need more than this, the lack of indexes is going to _really_ bite. :) Arne.