pgsql: Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably
Date
Msg-id 20080816022506.85037755315@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
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.

Modified Files:
--------------
    pgsql/src/bin/pg_dump:
        pg_backup_db.c (r1.79 -> r1.80)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_db.c?r1=1.79&r2=1.80)

pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Add to TODO: > > * Prevent query cancel packets from being
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix pg_dump/pg_restore's ExecuteSqlCommand() to behave suitably