| 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:50 |
| Message-ID: | 20090807201650.03C1575331E@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.
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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-08-07 20:50:22 | pgsql: Expand test coverage support to entire tree Test coverage |
| Previous Message | Tom Lane | 2009-08-07 20:16:41 | pgsql: Try to defend against the possibility that libpq is still in |