[Tickets #3471] RESOLVED: psql error when using turba

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=3471
-----------------------------------------------------------------------
 Ticket             | 3471
 Updated By         | Chris at VandenBerghe.org
 Summary            | psql error when using turba
 Queue              | Turba
 Version            | HEAD
 State              | Bogus
 Priority           | 1. Low
 Type               | Bug
 Owners             | Michael Rubinsky
-----------------------------------------------------------------------


Chris at VandenBerghe.org (2006-02-19 13:34) wrote:

Hi Michael,

> This is a configuration error: Based on your personal email to me 
> (relevent snippits below for reference) your datatree, indeed 
> everything that uses a database is broken due to an incorrect charset 
> setting for your database.  I corrected in your config using the test 
> login you provided.
>
> Please re-enable Turba to verify this is working for you now.

You were very right, the database encoding was indeed incorrect.  Thanks for
fixing this and sorry for the bogus bug report.

However, Turba still doesn't work properly.  The combination
Horde/IMP/Kronolith work just fine, enabling Turba makes the system
performance go down to an unusable level (minutes per page request!).  There
are no error message in the Horde log, psql log or Apache log... so, I'm in
the dark about what could cause this behavior.

The login is still enabled if you'd care to take a look.

Thanks,
Chris,