configuring schema using search path does not work well in pgbouncer in transaction mode

so I can't seem to find a way to use poll only mode with a custom search path behind pgbouncer/similar in transaction pooling mode.

the recommendation I have read is to use pgx "search_path" in order to configure the schema that the river clients will use.

but behind pgbouncer, search path is not supported, for technical reasons.

https://github.com/pgbouncer/pgbouncer/issues/89

we use an in-house rewrite of pgbouncer and so we made search path work correctly for session connections, which seems to be working, but tracking search path in transaction mode is a bigger lift so we haven't tried (as the search path isn't in parameters, you would need to do an extra query before giving the conn the session for the transaction to set the search path)

for now we are just going to run everything in session mode.

No repository files, tests, or implementation entry points are named. Start by investigating how River configures PostgreSQL search_path through pgx and how transaction pooling in PgBouncer affects that state; done would require a defined, tested way to configure the schema in transaction mode.