aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-08-07 20:16:29 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-08-07 20:16:29 +0000
commitb09e8b06670f84806a0102f25c1249e537398b1c (patch)
tree29e9ecc15f797a4444b219434ef0963b9f8260a7 /src/backend/access/gist/gistvacuum.c
parentaea7affde737d70da5cf0ffbc0c11bea323b81f4 (diff)
downloadpostgresql-b09e8b06670f84806a0102f25c1249e537398b1c.tar.gz
postgresql-b09e8b06670f84806a0102f25c1249e537398b1c.zip
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.
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions