[check_postgres] Two new patches

[Greg Sabino Mullane]

> The first one, pgbouncer.patch, allows us to check that pgbouncer
> configuration hasn't changed (same thing than the checksum-settings
> report).
...
> specific statement of pgbouncer. Would it be better if we create a full
> new report? or do you like it this way?

I think it would be better as a full report. This allows us to take 
things in different directions in the future if we enhance one or 
the other.

> The second one, nagios.patch, changes the field separator for unchecked
> objects (set with the warning parameter) on the same_schema report. We
> use a comma instead of a space because of our configuration of Nagios.
> Though I'm not sure this has a lot of value for other check_postgres
> users, I thought it would be better to let you decide if it could be
> interesting to integrate it.

I think this is probably harmless. Anyone else? If nobody pipes up, 
remind me in a day or so and I'll add it in.

-- 
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/2aae2b1a/attachment.bin