8.4: COPY continues after client disconnects

From: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: 8.4: COPY continues after client disconnects
Date: 2013-03-01 15:15:43
Message-ID: CAKuK5J3wYtQz1sfE4ZJ_vNfsFTk0HAcw5OBQvLFMK6jGf4guow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Using PostgreSQL 8.4.13 on ScientificLinux 6.3 (x86_64), I noticed
that a pg_dump ran out of (local) disk space.
However, the server was still using CPU and disk resources. An strace
clearly showed this pattern:

read(....) = 8192
sendto(...) = -1 EPIPE
-- SIGPIPE (Broken pipe) @ ....

The server does detect the broken pipe. It logs the following messages:

637 LOG: 08006: could not send data to client: Connection reset by peer
638 LOCATION: internal_flush, pqcomm.c:1108
639 STATEMENT: COPY ... to stdout;
640 LOG: 08006: could not send data to client: Broken pipe
641 LOCATION: internal_flush, pqcomm.c:1108
642 STATEMENT: COPY ... to stdout;

it ran until I killed it.

--
Jon

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message fburgess 2013-03-01 15:20:31 Re: Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space.
Previous Message dgplinux 2013-03-01 10:01:08 BUG #7911: Equal vertices are not identified