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:11
Message-ID: 20090807201611.C243E75331E@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
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.

Modified Files:
--------------
pgsql/src/bin/psql:
copy.c (r1.81 -> r1.82)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/copy.c?r1=1.81&r2=1.82)

Browse pgsql-committers by date

  From Date Subject
Next Message User Bmomjian 2009-08-07 20:16:12 pg-migrator - pg_migrator: Use the pre-initdb cutoff for testing
Previous Message User Bmomjian 2009-08-07 20:12:51 pg-migrator - pg_migrator: