[check_postgres] same_schema handle badly dbservice mixed with dbname option.

[Cédric Villemain]

Hello,

I find the following issue when using dbservice with same_schema action:

[dalibo at foo1 ~]$ ./check_postgres.pl --action same_schema   -H foo1 --dbuser 
superviseur -db bar --dbservice2=superviseur2 
ERROR: FATAL:  Ident authentication failed for user "postgres"
--> error

[dalibo at foo11 ~]$ ./check_postgres.pl --action same_schema  --
dbservice=superviseur -H2 foo2 --dbuser2 superviseur -db2 bar 
Use of uninitialized value in concatenation (.) or string at 
./check_postgres.pl line 1550
--> error

[dalibo at foo1 ~]$ ./check_postgres.pl --action same_schema  --
dbservice=superviseur --dbservice2=superviseur2 
-->success

There is probably something to do to handle those case, and perhaps provide a 
hash with all info accessible in the functions check_*. Actually %info doesn't 
not contain same things if you connect with dbservice or with ---dbname, and 
special case with multiple connection are not parsed properly. I can try to 
provide a patch but it is perhaps better to rework some core part of the code. 
Ideas ?

----
Cédric Villemain
Administrateur de Base de Données
Cel: +33 (0)6 74 15 56 53
http://dalibo.com - http://dalibo.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : https://mail.endcrypt.com/pipermail/check_postgres/attachments/20090624/d7db21f4/attachment.bin