8.4: COPY continues after client disconnects

Поиск
Список
Период
Сортировка
От Jon Nelson
Тема 8.4: COPY continues after client disconnects
Дата
Msg-id CAKuK5J3wYtQz1sfE4ZJ_vNfsFTk0HAcw5OBQvLFMK6jGf4guow@mail.gmail.com
обсуждение исходный текст
Ответы Re: 8.4: COPY continues after client disconnects  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Список 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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: dgplinux@yahoo.com
Дата:
Сообщение: BUG #7911: Equal vertices are not identified
Следующее
От:
Дата:
Сообщение: Re: Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space.