mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-01-12 18:34:36 +08:00
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.
This commit is contained in:
parent
aea7affde7
commit
b09e8b0667
@ -3,7 +3,7 @@
|
||||
*
|
||||
* Copyright (c) 2000-2006, PostgreSQL Global Development Group
|
||||
*
|
||||
* $PostgreSQL: pgsql/src/bin/psql/copy.c,v 1.71.2.1 2007/02/05 15:23:24 adunstan Exp $
|
||||
* $PostgreSQL: pgsql/src/bin/psql/copy.c,v 1.71.2.2 2009/08/07 20:16:29 tgl Exp $
|
||||
*/
|
||||
#include "postgres_fe.h"
|
||||
#include "copy.h"
|
||||
@ -603,6 +603,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, _("trying to exit copy mode"));
|
||||
PQclear(result);
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user