gen_random_uuid() creates a different UUID in each node of a replicated PostgreSQL environment when running Pgpool-II in native replication mode.
This has been reported for mod-configuration and Pgpool-II replication in #sys-ops on Slack. From the Pgpool-II manual:
There is no guarantee that any data provided using a context-dependent mechanism (e.g. random number, transaction ID, OID, SERIAL, sequence), will be replicated correctly on multiple backends.
RMB documentation mentions it in the upgrading guide for RMB 25 and in connection with "generateId": https://github.com/folio-org/raml-module-builder/#the-post-tenant-api
- Remove gen_random_uuid usage; use a hard-coded value, or generate UUID in Java
- Remove "CREATE EXTENSION pgcrypto"
This doesn't affect Pgpool-II streaming replication mode, only Pgpool-II native replication mode.