Add an ORDER BY to the slony_status check to account for cases in which

there is more than one node in replication; we want to report on the
most lagged server.

1 files changed, 2 insertions, 1 deletions

diff --git a/check_postgres.pl b/check_postgres.pl
index fae344f66..73a99c1e4 100755
--- a/check_postgres.pl
+++ b/check_postgres.pl
@@ -7421,7 +7421,8 @@ q{SELECT
  COALESCE(n2.no_comment, '') AS com2
 FROM SCHEMA.sl_status
 JOIN SCHEMA.sl_node n1 ON (n1.no_id=st_origin)
-JOIN SCHEMA.sl_node n2 ON (n2.no_id=st_received)};
+JOIN SCHEMA.sl_node n2 ON (n2.no_id=st_received)
+ORDER BY 1 DESC};
 
     my $maxlagtime = -1;