Disabling Prepared statements

[TheOtherBrian1]

It is important to note that although the direct connections and Supavisor in Session mode support prepared statements, Supavisor in transaction mode does not.

How to disable prepared statements for Supavisor in transaction mode

Each ORM or library configures prepared statements differently. Here are settings for some common ones. If you don't see yours, make a comment

Prisma:

add ?pgbouncer=true to end of connection string:

postgres://[db-user].[project-ref]:[db-password]@aws-0-[aws-region].pooler.supabase.com:6543/[db-name]?pgbouncer=true

Drizzle:

Add a prepared false flag to the client:

export const client = postgres(connectionString, { prepare: false })

#postgres.js
Set the prepare config to false

node postgres

Just omit the "name" value in a query definition:

const query = {
  name: 'fetch-user', // <--------- DO NOT INCLUDE
  text: 'SELECT * FROM user WHERE id = $1',
  values: [1],
}

psycopg

set the prepare_threshold to None.

asyncpg

Follow the recommendation in the asyncpg docs

disable automatic use of prepared statements by passing statement_cache_size=0 to asyncpg.connect() and asyncpg.create_pool() (and, obviously, avoid the use of Connection.prepare());

Rust's Deadpool or tokio-postgres:

• Check Github Discussion

[mirusky]

I'm having issues with GORM I've setted PrepareStmt to false as docs suggests.

I'll try the 'pgbouncer=true' at end of connection string to see if it takes in.

[TheOtherBrian1]

pgbouncer=true is how Prisma reconfigures prepared statements, but it would not have an impact on GORM. As the doc you shared pointed out, modifying the global and/or session configs to PrepareStmt: false should be sufficient.

Are you certain that the error is prepared statement related?

As an aside, I'm curious to know where you're deploying to: AWS Lambda, Render, Fly.io? Depending on whether the service auto-scales or is predominantly stationary, the direct connection or Supavisor in session mode may be better

[mirusky]

My logs show that it is related to the prepared stmt, but even disabling it explicitly continues to give an error. Especially after the app has restarted.

Maybe something related to GORM itself? I'll try to contact them.

[TheOtherBrian1]

I'll try to contact them.

@mirusky, I'd love if you could share their feedback. If we can add it to the list, that could be very helpful for others