Database relation does not exist proxy versus origin split response

When this happens

Use this when a cdn, load balancer, reverse proxy, or waf sits in front of the service. Do not stop at the screen message; validate whether the edge/proxy or the origin server creates the failure first.

Symptom checklist

• relation does not exist appears repeatedly in the Database UI or logs.
• slow query, locks, pool, index, charset differs between successful and failed requests.
• The issue appears only after separating SQL error from application transaction behavior.
• It often follows deploys, permission changes, configuration edits, or data refreshes.

Likely causes

• relation does not exist specifically changes the investigation surface for Database: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
• The query runs against a database, schema, or search_path that does not contain the expected relation.
• Migrations ran on primary or staging but not on the target database.
• Read traffic reaches a replica before replay catches up.
• A query filters or joins without a supporting index under production data volume.
• Connection pools are exhausted by slow transactions or leaked clients.
• For the proxy versus origin split case, the first useful clue is whether the edge/proxy or the origin server creates the failure.

First 1-minute checks

1. Write down the first failure time, latest change, affected user, path, and object ID.
2. Compare slow query, locks, pool, index, charset for success and failure in the same window.
3. Test the hypothesis: database failure caused by missing schema object, search_path drift, replica delay, missing index, or exhausted connection pool.
4. Classify this as proxy versus origin split: whether the edge/proxy or the origin server creates the failure.
5. Capture current values before changing configuration.

First evidence

Treat relation does not exist as a proxy versus origin split case. First collect evidence for whether the edge/proxy or the origin server creates the failure.

Output examples

Normal output

Direct origin and routed proxy return equivalent status and headers.

Failing output

Origin succeeds but proxy fails, or proxy succeeds while direct origin exposes the real backend error.

Output-to-action branches

• A CDN, load balancer, reverse proxy, or WAF sits in front of the service.
  Test direct origin and routed traffic separately, then change only the layer that differs.
• The working and failing outputs differ.
  Act on the differing layer first: For relation does not exist, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Command output is normal but users still fail.
  Separate browser cache, cookies, permissions, and network location before declaring it fixed.

Do not do this

• Do not assume the CDN error code is the application root cause.
• Do not change multiple layers before identifying the failing layer.
• Do not delete production data, grant broad permissions, or disable security controls as a first response.

Evidence quality

Auto-generated operator draft: includes issue-specific causes, commands, output branches, and unsafe-action warnings. Official-source links and real incident validation are queued for enrichment.

Commands to run first

grep -R "relation does not exist" ./logs

SHOW PROCESSLIST;

SHOW ENGINE INNODB STATUS\G

EXPLAIN SELECT ...

grep -R "relation does not exist" ./logs

psql -c "select current_database(), current_schema(), current_user"

psql -c "select relname from pg_class where relname like '%NAME%'"

psql -c "select * from pg_stat_replication"

mysql -e "show processlist"

curl -Iv https://example.com --resolve example.com:443:ORIGIN_IP

Fix order

1. Record the full relation does not exist message, failing URL, user, object ID, and latest change.
2. Collect issue-specific evidence for database failure caused by missing schema object, search_path drift, replica delay, missing index, or exhausted connection pool.
3. Compare the failing case with a successful case before editing settings.
4. If this is the proxy versus origin split branch, Test direct origin and routed traffic separately, then change only the layer that differs.
5. Re-check with the same command and URL, then record the normal output.

Actions by cause

• For relation does not exist, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Confirm current database, schema, user, and migration version before editing SQL.
• Apply migrations to the correct primary and verify relation visibility.
• Route read-after-write paths to primary or wait for replica replay.
• Use EXPLAIN ANALYZE and add the smallest useful index.
• Measure active, idle, and waiting connections before increasing pool size.
• For the proxy versus origin split branch, Test direct origin and routed traffic separately, then change only the layer that differs.

Evidence links

• MySQL error reference official
• PostgreSQL documentation official

Verification metadata

• operator-draft
• official-reference-linked
• 2026-07-23

Update queue

• Review cadence
  weekly-source-review
• Next enrichment
  Add one official-source check and one real output example for Database relation does not exist.

Environment-specific checks

• Shared hosting, proxies, VPNs, or CDN layers can change SQL error from application transaction behavior results.
• Do not trust only the Database UI; compare command output.
• Japanese hosting panels may show completion before DNS or SSL fully propagates.
• Test from both office and external networks.

Prevent it next time

• Store normal examples for slow query, locks, pool, index, charset.
• Add indexing, pool tuning, transaction scope, charset alignment to the release checklist.
• Keep recurring errors in the same note format.
• Split alerts by error rate, latency, certificates, disk, and permission changes.

Related notes

• MySQL Too many connections
• MySQL Duplicate entry fix note
• MySQL Deadlock fix note
• PostgreSQL relation does not exist fix note
• MySQL Duplicate entry fix note 2
• MySQL Deadlock fix note 2
• PostgreSQL relation does not exist fix note 2
• MySQL Duplicate entry fix note 3