Thanks to visit codestin.com
Credit goes to postgrespro.com

Request a Demo
Home   >   mailing lists

pgsql: Try to defend against the possibility that libpq is still in - Mailing list pgsql-committers

From [email protected] (Tom Lane)
Subject pgsql: Try to defend against the possibility that libpq is still in
Date
Msg-id [email protected]
Whole thread Raw
List pgsql-committers
Tree view 
Log Message:
-----------
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.

Tags:
----
REL7_4_STABLE

Modified Files:
--------------
    pgsql/src/bin/psql:
        copy.c (r1.33.4.2 -> r1.33.4.3)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/copy.c?r1=1.33.4.2&r2=1.33.4.3)

pgsql-committers by date:

Previous
From: [email protected] (Tom Lane)
Date:
Subject: pgsql: Try to defend against the possibility that libpq is still in
Next
From: [email protected] (Peter Eisentraut)
Date:
Subject: pgsql: Expand test coverage support to entire tree Test coverage