community.proxysql.proxysql_pgsql_query_rules module – Modifies pgsql query rules using the proxysql admin interface
Note
This module is part of the community.proxysql collection (version 1.8.0).
You might already have this collection installed if you are using the ansible package. It is not included in ansible-core. To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install community.proxysql. You need further requirements to be able to use this module, see Requirements for details.
To use it in a playbook, specify: community.proxysql.proxysql_pgsql_query_rules.
New in community.proxysql 1.8.0
Synopsis
- The community.proxysql.proxysql_pgsql_query_rules module modifies pgsql query rules using the proxysql admin interface.
Requirements
The below requirements are needed on the host that executes this module.
- PyMySQL
- mysqlclient
Parameters
Parameter | Comments |
|---|---|
active boolean | A rule with Choices:
|
apply boolean | Used in combination with flagIN and flagOUT to create chains of rules. Setting apply to True signifies the last rule to be applied. If omitted the proxysql database default for apply is Choices:
|
attributes string | A JSON field that can be used to specify load balancing between hostgroups based on query rules. If omitted the proxysql database default for attributes is |
cache_empty_result boolean | Controls if resultset without rows will be cached or not. Choices:
|
cache_timeout integer | The maximum timeout in milliseconds for caching the result of the query. |
cache_ttl integer | The number of milliseconds for which to cache the result of the query. |
client_addr string | Match traffic from a specific source. |
comment string | Free form text field, usable for a descriptive comment of the query rule. |
config_file path | Specify a config file from which login_user and login_password are to be read. Default: |
database string | Filtering criteria matching database. If database is non-NULL, a query will match only if the connection uses database as its default schema. |
delay integer | Number of milliseconds to delay the execution of the query. This is essentially a throttling mechanism and QoS, and allows a way to give priority to queries over others. |
destination_hostgroup integer | Route matched queries to this hostgroup. |
digest string | Match queries with a specific digest, as returned by stats_pgsql_query_digest.digest. |
error_msg string | Query will be blocked, and the specified error_msg will be returned to the client. |
flagIN integer | Used in combination with flagOUT and apply to create chains of rules. If omitted the proxysql database default for flagIN is |
flagOUT integer | Used in combination with flagIN and apply to create chains of rules. When set, flagOUT signifies the flagIN to be used in the next chain of rules. |
force_delete boolean | By default we avoid deleting more than one query rule in a single batch, however if you need this behaviour and you are not concerned about the query rules deleted, you can set force_delete to Choices:
|
load_to_runtime boolean | Dynamically load config to runtime memory. Choices:
|
log boolean | Query will be logged. Choices:
|
login_host string | The host used to connect to ProxySQL admin interface. Default: |
login_password string | The password used to authenticate to ProxySQL admin interface. |
login_port integer | The port used to connect to ProxySQL admin interface. Default: |
login_unix_socket string | The socket used to connect to ProxySQL admin interface. |
login_user string | The username used to authenticate to ProxySQL admin interface. |
match_digest string | Regular expression that matches the query digest. The dialect of regular expressions used is that of re2 - https://github.com/google/re2. |
match_pattern string | Regular expression that matches the query text. The dialect of regular expressions used is that of re2 - https://github.com/google/re2. |
mirror_flagOUT integer | Enables query mirroring. If set mirror_flagOUT can be used to evaluates the mirrored query against the specified chain of rules. |
mirror_hostgroup integer | Enables query mirroring. If set mirror_hostgroup can be used to mirror queries to the same or different hostgroup. |
multiplex integer | If If If By default, does not change multiplexing policies. Choices:
|
negate_match_pattern boolean | If negate_match_pattern is set to Choices:
|
next_query_flagIN integer | When is set, its value will become the flagIN value for the next queries. |
OK_msg string | The specified message will be returned for a query that uses the defined rule. |
proxy_addr string | Match incoming traffic on a specific local IP. |
proxy_port integer | Match incoming traffic on a specific local port. |
re_modifiers string | Comma separated list of options to modify the behavior of the RE engine. With |
reconnect boolean | Not yet implemented in ProxySQL. Choices:
|
replace_pattern string | This is the pattern with which to replace the matched pattern. Note that this is optional, and when omitted, the query processor will only cache, route, or set other parameters without rewriting. |
retries integer | The maximum number of times a query needs to be re-executed in case of detected failure during the execution of the query. |
rule_id integer | The unique id of the rule. Rules are processed in rule_id order. |
save_to_disk boolean | Save config to sqlite db on disk to persist the configuration. Choices:
|
state string | When Choices:
|
sticky_conn boolean | Not yet implemented in ProxySQL. Choices:
|
timeout integer | The maximum timeout in milliseconds with which the matched or rewritten query should be executed. If a query run for longer than the specific threshold, the query is automatically killed. |
username string | Filtering criteria matching username. If username is non-NULL, a query will match only if the connection is made with the correct username. |
Attributes
Attribute | Support | Description |
|---|---|---|
check_mode | Support: full | Do not make any changes to memory, disk, or runtime. |
Examples
---
# This example adds a rule to redirect queries from a specific user to another
# hostgroup, it saves the pgsql query rule config to disk, but avoids loading
# the pgsql query config to runtime (this might be because several rules are
# being added and the user wants to push the config to runtime in a single
# batch using the community.proxysql.proxysql_manage_config module). It uses
# supplied credentials to connect to the proxysql admin interface.
- name: Add a rule
community.proxysql.proxysql_pgsql_query_rules:
login_user: admin
login_password: admin
username: 'guest_ro'
match_pattern: "^SELECT.*"
destination_hostgroup: 1
active: 1
retries: 3
state: present
load_to_runtime: false
# This example removes all rules that use the username 'guest_ro', saves the
# pgsql query rule config to disk, and dynamically loads the pgsql query rule
# config to runtime. It uses credentials in a supplied config file to connect
# to the proxysql admin interface.
- name: Remove rules
community.proxysql.proxysql_pgsql_query_rules:
config_file: '~/proxysql.cnf'
username: 'guest_ro'
state: absent
force_delete: true
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key | Description |
|---|---|
stdout dictionary | The pgsql query rule modified or removed from proxysql. Returned: On create/update will return the newly modified rule, in all other cases will return a list of rules that match the supplied criteria. Sample: |
Collection links
© 2012–2018 Michael DeHaan
© 2018–2025 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/projects/ansible/latest/collections/community/proxysql/proxysql_pgsql_query_rules_module.html