The upstream FilesystemSessionStore does not do that.

Retry on OperationalError exception, which we receive on database restart.
Return cursor to pool when reconnecting.

There were concurrency issues in evented mode.
So while I was at it, I added support for threaded mode too.

If the connection to the database fails when
retrying a session operation, we end up
with no cursore, which makes subsequent
session operations fail.

We fix this by ensuring we have cursor
before any operations.

…gument 'max_lifetime'" when autovacuum gets executed.

Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>

It has been implemented.

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: server-tools-18.0/server-tools-18.0-session_db
Translate-URL: https://translation.odoo-community.org/projects/server-tools-18-0/server-tools-18-0-session_db/

with the parameter "login" in `_make_postgres_uri()` it becomes impossible to log in with the configured database, as it has to have the name "user". This is because of passing the `connection_info` dict as keywords parameter into the function. But because `connection_info_for` called in `setUp()` reads the config file of odoo and there the database user is `db_user` the keyword parameter is discarded and `login` is not set. The `db_`-prefix is removed. So user and password are not applied to the uri/dsn and thus login to the database is not possible, if the database wants those parameters.

When I applied this change in our internal CI of solute.de, everything worked fine afterwards.

This has to be ported to 17.0 and 18.0 as well.