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