Question 1

How do I set up ProxySQL for read/write splitting with MySQL?

Accepted Answer

Configure query rules in the admin interface to route SELECT queries to read replicas and INSERT/UPDATE queries to the primary server, using the mysql_query_rules table with match patterns and hostgroups.

Question 2

Is ProxySQL better than HAProxy for database load balancing?

Accepted Answer

ProxySQL is protocol-aware for MySQL and PostgreSQL, offering query-level routing and caching, whereas HAProxy is a general TCP proxy; choose ProxySQL for database-specific features and HAProxy for simpler connection-level balancing.

Question 3

How to enable query caching in ProxySQL to reduce database load?

Accepted Answer

Use the query cache functionality by configuring cache settings in the admin variables and defining rules in mysql_query_rules or pgsql_query_rules to cache frequent query results.

Question 4

Does ProxySQL work with PostgreSQL, and how is it configured?

Accepted Answer

Yes, ProxySQL supports PostgreSQL via the pgsql_variables, pgsql_servers, and pgsql_users tables in the admin interface, with configuration similar to MySQL but on port 6132 by default.

Question 5

What's the performance impact of ProxySQL on database latency?

Accepted Answer

ProxySQL adds minimal latency due to efficient connection pooling and caching, but overhead can vary based on rule complexity and traffic; benchmarks are available on the project's blog for reference.

Question 6

How to set up automatic failover in ProxySQL for high availability?

Accepted Answer

Configure backend servers in the mysql_servers or pgsql_servers table with monitoring enabled, so ProxySQL automatically reroutes traffic during failures based on health checks.

ProxySQL

What is ProxySQL?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions