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:23 +0000 (02:25 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Sat, 16 Aug 2008 02:25:23 +0000 (02:25 +0000)
commit7e9308544f041cf59e0dd4916fe93fee9aa91f99
tree8e7a3660a5c7f0eb0d5b64e810d28756773e4d3a
parent7a9b6cd47259e4d5ee4330e6b38fa021dbc111cd
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