while vacuum: pq_flush: send() failed: Broken pipe
while doing a vacuum, i got a 'broken pipe' error. is this serious?
...
DEBUG: Pages 1: Changed 0, reaped 1, Empty 0, New 0; Tup 2: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed
2, MinLen 1206, MaxLen 1499; Re-using: Free/Avail. Space
5444/0; EndEmpty/Avail. Pages 0/0. CPU
0.00s/0.00u sec.
DEBUG: Index pg_toast_16600_idx: Pages 2; Tuples 2: Deleted 0. CPU
0.00s/0.00u sec.
DEBUG: MoveOfflineLogs: remove 0000000300000072
DEBUG: MoveOfflineLogs: remove 0000000300000073
DEBUG: MoveOfflineLogs: remove 0000000300000074
DEBUG: MoveOfflineLogs: remove 0000000300000075
DEBUG: MoveOfflineLogs: remove 0000000300000076
DEBUG: MoveOfflineLogs: remove 0000000300000077
DEBUG: MoveOfflineLogs: remove 0000000300000078
DEBUG: MoveOfflineLogs: remove 0000000300000070
DEBUG: MoveOfflineLogs: remove 0000000300000071
pq_flush: send() failed: Broken pipe
pq_recvbuf: unexpected EOF on client connection
"Thomas T. Thai" <tom@minnesota.com> writes:
while doing a vacuum, i got a 'broken pipe' error. is this serious?
...
DEBUG: Pages 1: Changed 0, reaped 1, Empty 0, New 0; Tup 2: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed
2, MinLen 1206, MaxLen 1499; Re-using: Free/Avail. Space
5444/0; EndEmpty/Avail. Pages 0/0. CPU
0.00s/0.00u sec.
DEBUG: Index pg_toast_16600_idx: Pages 2; Tuples 2: Deleted 0. CPU
0.00s/0.00u sec.
DEBUG: MoveOfflineLogs: remove 0000000300000072
DEBUG: MoveOfflineLogs: remove 0000000300000073
DEBUG: MoveOfflineLogs: remove 0000000300000074
DEBUG: MoveOfflineLogs: remove 0000000300000075
DEBUG: MoveOfflineLogs: remove 0000000300000076
DEBUG: MoveOfflineLogs: remove 0000000300000077
DEBUG: MoveOfflineLogs: remove 0000000300000078
DEBUG: MoveOfflineLogs: remove 0000000300000070
DEBUG: MoveOfflineLogs: remove 0000000300000071
pq_flush: send() failed: Broken pipe
pq_recvbuf: unexpected EOF on client connection
Are you sure that's "while" doing the vacuum, and not "after"?
In any case, what this indicates is ungraceful disconnection by the
client. What client software was used to issue the vacuum command?
regards, tom lane
On Mon, 29 Jan 2001, Tom Lane wrote:
Date: Mon, 29 Jan 2001 01:57:29 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas T. Thai <tom@minnesota.com>
Cc: PostgreSQL General <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] while vacuum: pq_flush: send() failed: Broken pipe"Thomas T. Thai" <tom@minnesota.com> writes:
while doing a vacuum, i got a 'broken pipe' error. is this serious?
...
DEBUG: Pages 1: Changed 0, reaped 1, Empty 0, New 0; Tup 2: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed
2, MinLen 1206, MaxLen 1499; Re-using: Free/Avail. Space
5444/0; EndEmpty/Avail. Pages 0/0. CPU
0.00s/0.00u sec.
DEBUG: Index pg_toast_16600_idx: Pages 2; Tuples 2: Deleted 0. CPU
0.00s/0.00u sec.
DEBUG: MoveOfflineLogs: remove 0000000300000072
DEBUG: MoveOfflineLogs: remove 0000000300000073
DEBUG: MoveOfflineLogs: remove 0000000300000074
DEBUG: MoveOfflineLogs: remove 0000000300000075
DEBUG: MoveOfflineLogs: remove 0000000300000076
DEBUG: MoveOfflineLogs: remove 0000000300000077
DEBUG: MoveOfflineLogs: remove 0000000300000078
DEBUG: MoveOfflineLogs: remove 0000000300000070
DEBUG: MoveOfflineLogs: remove 0000000300000071
pq_flush: send() failed: Broken pipe
pq_recvbuf: unexpected EOF on client connectionAre you sure that's "while" doing the vacuum, and not "after"?
In any case, what this indicates is ungraceful disconnection by the
client. What client software was used to issue the vacuum command?
client was from psql. i saw that appear in the log by doing tail -f before
i saw the word VACUUM.. but it was right about the same time.
"Thomas T. Thai" <tom@minnesota.com> writes:
pq_flush: send() failed: Broken pipe
pq_recvbuf: unexpected EOF on client connectionAre you sure that's "while" doing the vacuum, and not "after"?
In any case, what this indicates is ungraceful disconnection by the
client. What client software was used to issue the vacuum command?
client was from psql. i saw that appear in the log by doing tail -f before
i saw the word VACUUM.. but it was right about the same time.
If the psql process didn't betray any unhappiness, then the broken-pipe
error isn't referring to the psql connection. What other clients were
running?
regards, tom lane