Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably if PQexec
authorTom Lane <[email protected]>
Sat, 16 Aug 2008 02:25:23 +0000 (02:25 +0000)
committerTom Lane <[email protected]>
Sat, 16 Aug 2008 02:25:23 +0000 (02:25 +0000)
commit9fd16124988934ada4a91e42408e916896bbf2d4
tree5e7109a5c1abcb48d552a23477b5953516132d36
parent2be7cd82b5d735ddac141399b7acccad3abad8bc
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