{"version":"2.1.295","anchor":"gateway-warns-when-postgres-is-read-only","canonical_anchor":"gateway-warns-when-postgres-is-read-only","heading":"Gateway now warns clearly when its Postgres database is read-only","tier":"notice","area":"LLM Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/gateway-warns-when-postgres-is-read-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Gateway now warns clearly when its Postgres database is read-only\n\nWhen the gateway's Postgres database cannot be written to, the gateway now logs a warning naming the cause and how to fix it\n\n**What**\n\nThe gateway can keep its data in a Postgres database, set with `store.postgres_url`. When that database is read-only, the gateway now logs a specific warning instead of a general one. A database is read-only when it is a standby copy, or when its `default_transaction_read_only` option is on. The warning says:\n\n- New sign-ins fail.\n\n- Spending is not recorded.\n\n- `store.postgres_url` should point at a database server that accepts writes.\n\n- The copy of the gateway should be restarted if the warning keeps appearing.\n\nBefore, this case showed up only as a general message that a cleanup step had failed.\n\n**Why**\n\nIf you run the gateway, you now get a direct explanation for this failure and a fix, rather than a cleanup error that does not say what went wrong.\n\n- Area: LLM Gateway\n- Names: `store.postgres_url`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}