Skip site navigation (1) Skip section navigation (2)

pgsql: Try to defend against the possibility that libpq is still in

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Try to defend against the possibility that libpq is still in
Date: 2009-08-07 20:16:16
Message-ID: 20090807201616.4D2CA75331E@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
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:
----
REL8_4_STABLE

Modified Files:
--------------
    pgsql/src/bin/psql:
        copy.c (r1.80 -> r1.80.2.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/copy.c?r1=1.80&r2=1.80.2.1)

pgsql-committers by date

Next:From: Tom LaneDate: 2009-08-07 20:16:22
Subject: pgsql: Try to defend against the possibility that libpq is still in
Previous:From: User BmomjianDate: 2009-08-07 20:16:12
Subject: pg-migrator - pg_migrator: Use the pre-initdb cutoff for testing

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group