-
Notifications
You must be signed in to change notification settings - Fork 64
Usage with pg-bouncer
#410
Comments
Related issue: prisma/prisma#556 |
I'll write a document about pgbouncer today. |
Summary: yes we can. The work so far in two branches: |
Merged to master now, instructions how to enable the transaction mode in query engine can be found here: |
Threw this back to @timsuchanek now. You should make a decision how and when to enable the flag in query engine, if wanting to support pgbouncer transaction mode in the client. |
We now run all the tests against pgbouncer in transaction mode btw. |
I did an initial test how Heroku's Pgbouncer offering could work together with Prisma. Summarizing what needs to be done for Pgbouncer: If in If in
And of course the Prisma Client needs to start the server in the right mode, e.g. this spec should be implemented. Heroku allows changing Pgbouncer's settings using environment variables. For now only two of the three settings can be changed: > heroku config:add PGBOUNCER_POOL_MODE=transaction
> heroku config:add PGBOUNCER_SERVER_RESET_QUERY="DEALLOCATE ALL" The third setting should be available when the needed pull request lands. For other important providers, as discussed with @divyenduz, he will make sure the settings are available. When all is set, these need to be communicated with our users through the documentation. |
We should research how to set up Prisma Client together with
pg-bouncer
.The text was updated successfully, but these errors were encountered: