Peter Eisentraut

The problem with that query is that if there is no write activity on the primary, the `pg_last_xact_replay_timestamp()` doesn't advance, and then the reported value grows without bounds.

I'm not sure, but even if that worked, it would require using archiving, which would be a problematic requirement.

I don't think there is built-in support for monitoring pglogical. The way to monitor pglogical would be to use a `custom_query` check against the various views that are available. The...

seeing the same thing

What does your `brew tap` show?

Here is a thread that discusses why most of the proposed launchd.plist solutions are faulty: http://www.postgresql.org/message-id/[email protected]

`brew postgresql-upgrade-database` is not something from this repository. You should report issues with it to the Homebrew core repositories.

You will find the `postgres` executable at `/usr/local/opt/postgresql@14/bin/postgres` or analogously for other versions.

Can you post the entire `configure` output and perhaps even `config.log`. Maybe the system Perl and libxml installations have changed in Mojave. Or perhaps a matching XCode update is needed.

So according to `config.log`, there is a `perl.h`, which includes `EXTERN.h`, which is missing. Take a look around `/System/Library/Perl/5.18/darwin-thread-multi-2level/CORE/` to see what's going on there. Maybe after the upgrade there...