[check_postgres] slony status check broke between 2.16.0 and 2.19.0. it no longer checks all replication sets. now it only checks one.

[Aleksey Tsalolikhin]

Hi.  Thank you for check_postgres.pl, it's very useful in keeping our
DB running smoothly.  I love it.

Today I upgraded from 2.16.0 to 2.19.0 and my "slony_status" check
stopped checking all my replication sets.  Now it only checks one of
them.  Is there some way to get the old behavior please?

2.19.0:

# check_postgres.pl --action=slony_status --host=a.b.c.d -db myDB
POSTGRES_SLONY_STATUS OK: DB "myDB" schema:_alchemy_cluster
(host:a.b.c.d) Slony lag time: 4 (4 seconds) | time=0.04s
'myDB._alchemy_cluster Node 1(Master Hollywood) -> Node 3(Slave1
Hollywood)'=4;60;300
#


2.16.0:

# check_postgres.pl-2.16.0 --action=slony_status --host=a.b.c.d -db myDB
POSTGRES_SLONY_STATUS CRITICAL: (host:a.b.c.d) Slony lag time: 9993 (2
hours 46 minutes) | time=0.04 'myDB Node 1(Master Hollywood) -> Node
2(Slave Burbank)'=9993;60;300
'myDB Node 1(Master Hollywood) -> Node 3(Slave1 Hollywood)'=8;60;300
'myDB Node 1(Master Hollywood) -> Node 4(Slave2 Hollywood)'=6;60;300
#

Thanks again for a great tool.

Yours,
Aleksey