Bug 1031580

Description of problem:
backup.sh and restore.sh do not work by default (default pg_hba.conf) at all. It is neither intuitive how to solve it nor it is clever to ask me for password.

(Enterprise means being dumb and user friendly by default.)

Customer does not need to be PSQL expert to just execute backup, would he know about PGPASSWORD? But even with PGPASSWORD it does not work for me.

# egrep -v "^#|^[ \t]*$" /var/lib/pgsql/data/pg_hba.conf
local   all         all                               ident
host    engine          engine          0.0.0.0/0               md5
host    engine          engine          ::0/0                   md5
host    all         all         127.0.0.1/32          ident
host    all         all         ::1/128               ident

# export PGPASSWORD=123456
# ./backup.sh -d engine -u engine -v -l /root/ -f backup-`date "+%Y%m%d%H%M"`.sql
Backup of database engine to /root//backup-201311181132.sql started...
pg_dump: [archiver (db)] connection to database "engine" failed: FATAL:  password authentication failed for user "engine"
pg_dump: *** aborted because of error
Backup of database engine failed.

Some more complains:
https://bugzilla.redhat.com/show_bug.cgi?id=976337#c10

Version-Release number of selected component (if applicable):
is23

How reproducible:
100%

Steps to Reproduce:
1. yum install rhevm
2. engine-setup
3. execute ./backup.sh (as above)

Actual results:
impossible

Expected results:
should be clever enough to guide me how to use it or it should ask me for password

Additional info:
using backup.sh and restore.sh should work without any hidden kung-fu. if one would need to change config, type undocumented (in -h output sense) environment variable, then this user could use non-paid upstream as enterprise friendliness of paid product is disputable.