[check_postgres] Patch to fix an issue with slony_status report when one uses a service to connect

[Greg Sabino Mullane]

> Once again, it happens only when you use --dbservice option. When
> someone use this option, $db->{dbname} is not initialized. (I said "Once
> again" because we already had the issue with the vacuum/analyze report.
> My patch is a modified copy of the one I sent for the vacuum/analyze
> report issue.)
> 
> The patch attached fixes it.

Thanks! I tweaked the regex a little bit and moved the database call to 
after the three important numbers. Pushed to git if you want to test.

That "once again" sounds like we need to add a unit test to make sure 
we don't have this keep happening...

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
Url : https://mail.endcrypt.com/pipermail/check_postgres/attachments/20100302/34bd67f2/attachment.bin