[check_postgres] Two new patches

[Guillaume Lelarge]

Le 02/03/2010 17:36, Greg Sabino Mullane a écrit :
>> 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.
> 

OK. I do agree with you. You'll find a new patch attached to this mail.
It adds the pgbouncer_settings_checksum report.

>> 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.
> 

Be sure I will :)


-- 
Guillaume.
 http://www.postgresqlfr.org
 http://dalibo.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgbouncer_settings_checksum.patch
Type: text/x-patch
Size: 5250 bytes
Desc: not available
Url : https://mail.endcrypt.com/pipermail/check_postgres/attachments/20100302/2b6e9659/attachment.bin