Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably if PQexec
commit8dcd6243aa4fd6901660e3af15f3b63ad41bed3e
authortgl <tgl>
Sat, 16 Aug 2008 02:25:06 +0000 (16 02:25 +0000)
committertgl <tgl>
Sat, 16 Aug 2008 02:25:06 +0000 (16 02:25 +0000)
tree8928ee5c9efc531e78f062b63a9cecb986f1e0ff
parent5c2b1bab07d550ea36e9faa1f43f78c1bb531acc
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