MySQL Proxy SQL Routing Failed
MySQL ProxySQL routes queries to wrong host when query rules are misconfigured.
Category archive
Published troubleshooting guides for database issues.
MySQL ProxySQL routes queries to wrong host when query rules are misconfigured.
PostgreSQL PgBouncer cannot allocate server connections when pool_size is too small.
MySQL Performance Schema causes overhead when too many instruments are enabled.
PostgreSQL statistics collector is not running when track_activities or track_counts is disabled.
MySQL query cache fragmentation reduces hit rate when many small queries cause fragmentation.
PostgreSQL uses suboptimal cached plan when table statistics have changed significantly.
MySQL cannot prepare new statements when prepared statement cache limit is reached.
PostgreSQL cursor cannot scroll backward when declared without SCROLL option.
MySQL rejects insert or update on view when data would not be visible through the view.
PostgreSQL materialized view returns outdated data when REFRESH has not been scheduled.
MySQL cannot update generated column when expression references non-deterministic function.
PostgreSQL array containment queries are slow when GIN index on array column is missing.
MySQL spatial index is ignored when query uses unsupported functions or data types.
PostgreSQL PostGIS spatial queries are slow when GiST index is not used or statistics are stale.
MySQL JSON extraction queries are slow when virtual columns or indexes are not defined.
PostgreSQL full text search returns no results when GIN index is not built or text search config is wrong.
MySQL rejects invalid data values when STRICT_TRANS_TABLES or STRICT_ALL_TABLES is enabled.
PostgreSQL RLS policies are bypassed when superuser or table owner accesses data.
MySQL query fails when comparing columns with different character sets or collations.
PostgreSQL character conversion fails when client encoding differs from database encoding.
MySQL auto-increment column reaches maximum value and cannot generate new IDs.
PostgreSQL sequence generates duplicate values when not synchronized with table data.
MySQL query scans all partitions when partition pruning conditions are not satisfied.
PostgreSQL TOAST table storing large values becomes corrupted after hardware failure.
MySQL InnoDB refuses to start when ib_logfile size does not match configuration.
PostgreSQL checkpoints take too long when checkpoint_timeout or checkpoint_completion_target is misconfigured.
MySQL table fragmentation degrades performance when OPTIMIZE TABLE has not been run.
PostgreSQL table has excessive bloat when VACUUM cannot keep pace with UPDATE/DELETE operations.
MySQL Router cannot route connections when InnoDB Cluster topology is unavailable.
PostgreSQL pgLogical replication fails when origin or target database is unreachable.
MySQL group replication member is excluded due to network partition or certification failure.
PostgreSQL logical replication slot becomes inactive when consumer disconnects or WAL is removed.
MySQL federated table cannot connect to remote server due to network or authentication issues.
PostgreSQL FDW query fails when remote server is unreachable or credentials are invalid.
MySQL SSL handshake fails when certificates are expired or cipher suites do not match.
PostgreSQL SSL connection fails due to certificate verification or protocol mismatch.
MySQL InnoDB table is corrupted after crash or storage failure requiring recovery.
PostgreSQL approaches transaction ID wraparound when vacuum has not run for extended period.
MySQL slow query performs full table scan when index cannot be used for the query pattern.
PostgreSQL query planner chooses sequential scan over index due to stale statistics or cost estimates.
MySQL InnoDB buffer pool hit rate drops when pool size is too small for working dataset.
PostgreSQL autovacuum fails to run due to configuration issues or long-running transactions.
MySQL binary logs consume all disk space when purge is disabled or replication is lagging.
PostgreSQL WAL segments consume all disk space when archiving fails or replication is stuck.
MySQL slave replication stops due to duplicate key errors or relay log corruption.
PostgreSQL standby replica falls behind primary due to write throughput or network latency.
MySQL detects deadlock when two transactions wait for locks held by each other.
PostgreSQL queries timeout waiting for locks when transactions hold conflicting locks.
MySQL server returns too many connections error when connection limit is reached.
PostgreSQL rejects new connections when max_connections is reached or connection pool is exhausted.