You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, syncious (due to using prepared statements) doesn't support pgbouncer in transaction mode.
My Invidious instance is rather big, so using pgbouncer for all db connections became an absolute must at some point. I would like sycious to use the connection pool of pgbouncer too, instead of using direct connections. I often have daily db connection spikes (during which pgboucner uses an additional reserve pool) and fear that syncious will at some point run into problems when using direct connections.
Request: Please make syncious pgbouncer compatible.
You could add do this by changing the db connection string as follows:
'{"host": "invidious-db", "port": 5432, "database": "invidious", "user": "kemal", "password": "kemal", "pgbouncer": true}'
And then change your code so that prepared statements aren't used when pgbouncer is set to true.
Cheers
The text was updated successfully, but these errors were encountered:
Currently, syncious (due to using prepared statements) doesn't support pgbouncer in transaction mode.
My Invidious instance is rather big, so using pgbouncer for all db connections became an absolute must at some point. I would like sycious to use the connection pool of pgbouncer too, instead of using direct connections. I often have daily db connection spikes (during which pgboucner uses an additional reserve pool) and fear that syncious will at some point run into problems when using direct connections.
Request: Please make syncious pgbouncer compatible.
You could add do this by changing the db connection string as follows:
'{"host": "invidious-db", "port": 5432, "database": "invidious", "user": "kemal", "password": "kemal", "pgbouncer": true}'
And then change your code so that prepared statements aren't used when pgbouncer is set to true.
Cheers
The text was updated successfully, but these errors were encountered: