Recently at work, I needed to be able to rewrite some postgresql queries which were coming from a closed-source application in order to integrate the app into our own system testing setup. Specifically I needed to replace instances of
current_timestamp with invocation of
I found a couple of options to do this:
- pgbouncer-rr is a patch for pgbouncer, initially written by AWS labs, which extends pgbouncer to include rewrite and rerouting capability.
- pg_query_rewrite is an extension for postgres, which supports substitution of an entire matching query with another one.
Unfortunately I hit some roadblocks with each.
pg_query_rewrite simply wasn’t flexible enough. I needed to do a string substitution on the query, not entire query replacement as I didn’t have the exact set of every query the application would issue. Also providers of managed postgresql instances like Google Cloud or AWS won’t let you install your own extensions.
pgbouncer-rr was moderately difficult to configure given that I only wanted a single feature (rewriting) and none of the usual things pgbouncer is used for (connection pooling, load balancing).
In the end, I found a neat library pgproto3 which implements the postgresql wire format and can be used to write both a client and server! I used this to write an application that can act as a proxy to a postgresql server and will rewrite the queries before forwarding them. The proxy approach seems more flexible than an extension as it can be bundled either on the application server, or on the database server, or somewhere in-between depending on the requirement.
At the moment this application only supports simple string replacement, but I hope to extend it with LUA support soon for arbitrary query rewriting.