Hi,
I'm a PostgreSQL DBA and I just learned about DBMail a few hours ago.
The first thing I noticed is that it has some trouble with PG 8.3, which
will hit stable within the next days. So far I noticed 4 problems:
- Implicit text casts are gone with 8.3.
Please see
http://www.postgresql.org/docs/8.3/static/release-8-3.html
E.1.2.1. General
This causes at least a problem with dbmail_aliases.deliver_to while
creating a new user.
- Invalid input syntax for bytea.
This happens only with some mails. Bytea handling changed with 8.3 as
well, but I'm currently unsure where exactly the problem is.
- Transactions management seems to lose track after database errors
A few "WARNING: there is already a transaction in progress" messages.
- A ton of escape string warnings, however this can be suppressed with
SET escape_string_warning = off;
I digged a bit through the source and hacked some stuff to get it going.
However is there any ETA for official 8.3 support?
In general I have a couple of questions about the schema. Some scary
things like:
DEFAULT '1979-11-03 22:05:58'::timestamp without time zone NOT NULL,
DEFAULT ''::character varying NOT NULL
caught my eye, but I guess this is to make it behave more MySQL like?
Another thing is:
p.data HAVING ENCODE(p.data::bytea,'escape') LIKE '%search%';
while I see that this works around UTF-8 encoding errors it's really
something that IMHO screams for a proper solution. I'll try if I can
come up with something. Since TSearch2 went in-core with 8.3 I'd like to
implement IMAP searching with it anyway. I'm aware that IMAP RFC
requires partial string matching, but iSpell with compound word support
makes it more bearable for a start. If real partial string matching is
required this can be archived with an additional lexem table.
Thanks for creating this project.
--
Best regards,
Hannes Dorbath
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
