Fix database parameters for PgBouncer compatibility
Remove PostgreSQL session-specific parameters that are not supported by PgBouncer connection pooling. Keep only application_name parameter which is passed through properly. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
parent
7fa41b85b4
commit
4fcdc33ec0
1 changed files with 2 additions and 9 deletions
|
|
@ -82,17 +82,10 @@ if config_env() == :prod do
|
|||
# Optimize for unnamed prepared statements (better for dynamic queries)
|
||||
prepare: :unnamed,
|
||||
# Connection parameters to leverage PostgreSQL settings
|
||||
# Note: When using PgBouncer, only certain parameters are supported
|
||||
parameters: [
|
||||
# Application name for monitoring
|
||||
application_name: "aprsme",
|
||||
# Leverage synchronous_commit=off in postgresql.conf
|
||||
synchronous_commit: "off",
|
||||
# Match work_mem setting
|
||||
work_mem: "16MB",
|
||||
# Statement timeout as safety net
|
||||
statement_timeout: "30s",
|
||||
# Prevent idle transactions
|
||||
idle_in_transaction_session_timeout: "60s"
|
||||
application_name: "aprsme"
|
||||
]
|
||||
|
||||
config :aprsme, AprsmeWeb.Endpoint,
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue