Skip to content
This repository was archived by the owner on Jan 14, 2021. It is now read-only.
This repository was archived by the owner on Jan 14, 2021. It is now read-only.

Ability to use Heroku's pgbouncer #628

Closed
Closed
Ability to use Heroku's pgbouncer#628
Assignees
janpio
Labels
kind/improvementAn improvement to existing feature and code.topic: pgbouncer
Milestone
Beta 6
@chrisdrackett

Description

@chrisdrackett
chrisdrackett
opened on Apr 2, 2020

Heroku has a pgbouncer that is one line to install (https://devcenter.heroku.com/articles/postgres-connection-pooling).

Currently its options do not seem to line up 100% with the requirements of prisma and it isn't possible to change them.

server_reset_query = DISCARD ALL
 server_reset_query_always = 0

When running we see errors like the following:

2020-04-02T17:29:11+00:00 app[postgres.13791]: [AMBER] [11-1]  sql_error_code = 42P05 ERROR:  prepared statement "s3" already exists
2020-04-02T17:29:11+00:00 app[postgres.13791]: [AMBER] [11-2]  sql_error_code = 42P05 STATEMENT:  UPDATE "public"."Log" SET "ownerId" = $1, "type" = $2, "id" = $3, "updatedAt" = $4, "createdAt" = $5, "date" = $6 WHERE "public"."Log"."id" IN ($7)

Not sure if this would be possible to support, but it would be nice to use this vs. setting up and running our own instance of pgbouncer if at all possible!

Metadata

Metadata

Assignees

Labels

kind/improvementAn improvement to existing feature and code.topic: pgbouncer

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions