Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably if PQexec
authorTom Lane <tgl@sss.pgh.pa.us>
Sat, 16 Aug 2008 02:25:11 +0000 (02:25 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Sat, 16 Aug 2008 02:25:11 +0000 (02:25 +0000)
commit9a126217c60c4d54d9dcaf49b05edbffca65c9c9
tree85a48a28daa4d644a6eb044d3eaeb24741205a47
parent60a17b4fb211aef20a51acadf329c8c3be38f8a7
Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably if PQexec
returns NULL instead of a PGresult.  The former coding would fail, which
is OK, but it neglected to give you the PQerrorMessage that might tell
you why.  In the oldest branches, there was another problem: it'd sometimes
report PQerrorMessage from the wrong connection.
src/bin/pg_dump/pg_backup_db.c