graham/aprs.me
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix database parameters for PgBouncer compatibility

Browse source 
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:
Graham McIntire 2025-07-26 10:32:53 -05:00
parent 7fa41b85b4
commit 4fcdc33ec0
No known key found for this signature in database
1 changed files with 2 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
config/runtime.exs
View file

@ -82,17 +82,10 @@ if config_env() == :prod do
# Optimize for unnamed prepared statements (better for dynamic queries) # Optimize for unnamed prepared statements (better for dynamic queries)
prepare: :unnamed, prepare: :unnamed,
# Connection parameters to leverage PostgreSQL settings # Connection parameters to leverage PostgreSQL settings
# Note: When using PgBouncer, only certain parameters are supported
parameters: [ parameters: [
# Application name for monitoring # Application name for monitoring
application_name: "aprsme", 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"
] ]
config :aprsme, AprsmeWeb.Endpoint, config :aprsme, AprsmeWeb.Endpoint,