Search path occasionally reverts to public for PG connection with custom schema defined about lucid HOT 3 OPEN

Did some more testing; this seems related to my using digitalocean's connection pooler rather than lucid/knex's. I guess I'm occasionally getting connections without the search path set when pooling this way.

from lucid.

Hey @shaheedazaad! 👋🏻

How are you defining your searchPath? If you are mutating the global configuration, it is normal that you may encounter race conditioning between your requests.

Keep note that Node.js is processing multiple requests at the same time.

from lucid.

Hi @RomainLanz !

I'm defining separate connections for each search path, these are registered in a middleware based on the subdomain:
db.manager.add('tenant_' + tenantName, config)

I'm using the HttpContext to store the connection name and modifying the query client as suggested in the docs. In other words, I specify the connection for each query, which I think avoids the race condition problem - at least this is what my testing has shown so far.

The db emitter shows that the correct registered connection is always used, but the schema is reset to public. I don't actually have any other connections with the schema unset, or set to public.

from lucid.