I've set up SOGo server on Archlinux, with postgresql as database backend and auth through postgresql (using local socket). One test user has been set up in said table.

Next step is to run the test suite of my python caldav client library towards SOGo.

Now the test code should be optimized - it's almost silly, I have a global list of all calendars, event UID etc that are in use by at least one of the tests. For every test I do cleanup both before and after the test has run, going through every object on that global list, and ensure to delete it from the server if it exists on the server. The result is that when running the tests, the server gets bombarded with requests. But it's all serial, single-user, one request at the time.

So, like half of the tests run without problems, but then the rest fails on 501s from the server.

Digging more into it, the problem is that postgresql has run out of connection slots. It has hundred connection slots, I think that ought to suffice.

Digging even more into it, it seems that for every CalDAV query I'm doing from the tests, the SOGo server will open a new connection towards postgresql, but this connection is never closed.

(This may possibly be a duplicate of 0004083)