Where to Go Next¶

You have now covered everything in the User Guide. Here is where to go depending on what you need next.

A comprehensive worked example¶

The Worked Example book contains a complete, hands-on series of steps for creating and enabling objects in your own database, all wired up to pg_relay. It demonstrates the value pg_relay can deliver and shows you how to use it in a range of situations to build a more responsive database design.

Everything else lives in the Technical Guide¶

The Technical Guide covers everything that is not in this guide:

Running multiple Processors — for higher throughput and resilience.
Workers — the --workers flag, and when to use more than one.
The security model — how SECURITY DEFINER, SECURITY INVOKER, private tables, and action SQL isolation work together.
High availability — standby databases and multi-master clusters.
Connection poolers — why the Processor must connect directly to PostgreSQL.
The complete function reference — every function, its parameters, and what it returns.
Building from source — compiling the Processor binary yourself.
Platform support — the full list of tested and supported configurations.
Log levels and log format — what each log message means.
Self-scheduling maintenance — using pg_relay to run its own purge jobs.

Running on a managed cloud database?¶

See the Cloud Setup book for AWS, Azure, Google Cloud, and other managed providers.

Running more than one active database?¶

See the Multi-Master Deployment book.

Support¶

pg_relay is published and maintained by Pebble IT Solutions Pty Ltd, Australia.

Source and releases: gitlab.com/pebble-it/pg_relay
Issue tracker: gitlab.com/pebble-it/pg_relay/-/issues
Licence: MIT — see the Licence book.