On the self-hosted instance, I see these errors appear quite often. What it is?
02 Aug 2023 18:30:18:397 +0000 | ERROR | pid: cbf1c137-e9a8-440c-899f-a3aa49318855 | [pool-1-thread-4] thread | io.supertokens.multitenancy.MultitenancyHelper.lambda$refreshTenantsInCoreBasedOnChangesInCoreConfigOrIfTenantListChanged$0(MultitenancyHelper.java:145) | Tenant(, public, public) | io.supertokens.pluginInterface.exceptions.StorageQueryException: org.postgresql.util.PSQLException: ERROR: prepared statement "S_5" already exists
And these:
02 Aug 2023 18:29:28:160 +0000 | ERROR | pid: cbf1c137-e9a8-440c-899f-a3aa49318855 | [http-nio-0.0.0.0-3567-exec-6] thread | io.supertokens.webserver.WebserverAPI.service(WebserverAPI.java:445) | Tenant(, public, public) | jakarta.servlet.ServletException: io.supertokens.pluginInterface.exceptions.StorageQueryException: org.postgresql.util.PSQLException: ERROR: bind message supplies 3 parameters, but prepared statement "S_7" requires 0
Also, I'm using
https://neon.tech and I can see that supertoken always makes calls to the database or so, and that my computes are up as supertoken seems to ping it or try to do some queries or so. My app is before the release, so there are no clients and there are no calls to the database at all (I can see that by logs). So it's not my app that keeps computes alive.
Is there a way to disable such pinging of the database? At least for the dev instance of supertoken that would be quite useful to save some money here.