Joerg, I had this problem MANY times. Most often it was:
- the service account lost it privilege to log on as a service we suspect it were some interfering group policies. It was possible to "reactivate" by opening service control panel, reappling password. Windows then reported, that the "log on as service privilege" was granted. It worked again for some days. Final solution was to build a domain account which belongs to the "logon as service" group. that is NOT a postgreSQL problem, as long talks with magnus revealed ... the rights are lost within windows, and postgreSQL-Service-Account does NOT have privileges to change these rights. So, maybe this problem which eat much of my time is the same with you.. Harald -- GHUM Harald Massa persuasion python postgresql Harald Armin Massa Reinsburgstraße 202b 70197 Stuttgart 0173/9409607 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match