aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-08-07 20:16:49 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-08-07 20:16:49 +0000
commit6119329e236abc51f7da6e3f12a08e0b1448bade (patch)
tree4d9942bbfdc2ba83a49129ede8e22a6066521ac8
parent34f662dd65141990508ecb9e482cc4c9db50db4f (diff)
downloadpostgresql-6119329e236abc51f7da6e3f12a08e0b1448bade.tar.gz
postgresql-6119329e236abc51f7da6e3f12a08e0b1448bade.zip
Try to defend against the possibility that libpq is still in COPY_IN state
when we reach the post-COPY "pump it dry" error recovery code that was added 2006-11-24. Per a report from Neil Best, there is at least one code path in which this occurs, leading to an infinite loop in code that's supposed to be making it more robust not less so. A reasonable response seems to be to call PQputCopyEnd() again, so let's try that. Back-patch to all versions that contain the cleanup loop.
-rw-r--r--src/bin/psql/copy.c5
1 files changed, 4 insertions, 1 deletions
diff --git a/src/bin/psql/copy.c b/src/bin/psql/copy.c
index 925940e84d4..6742987ae5d 100644
--- a/src/bin/psql/copy.c
+++ b/src/bin/psql/copy.c
@@ -3,7 +3,7 @@
*
* Copyright (c) 2000-2003, PostgreSQL Global Development Group
*
- * $Header: /cvsroot/pgsql/src/bin/psql/copy.c,v 1.33.4.2 2006/11/24 23:07:07 tgl Exp $
+ * $Header: /cvsroot/pgsql/src/bin/psql/copy.c,v 1.33.4.3 2009/08/07 20:16:49 tgl Exp $
*/
#include "postgres_fe.h"
#include "copy.h"
@@ -425,6 +425,9 @@ do_copy(const char *args)
success = false;
psql_error("\\copy: unexpected response (%d)\n",
PQresultStatus(result));
+ /* if still in COPY IN state, try to get out of it */
+ if (PQresultStatus(result) == PGRES_COPY_IN)
+ PQputCopyEnd(pset.db, gettext("trying to exit copy mode"));
PQclear(result);
}