Hi all,
Are the below lines related with a disrupted client connection and a bad backend behaviour? That's what I think. I used to fetch these lines con pgadmin III connections.
Anyway, I have the idea of a bad hardware, well known here due to a DELL box hosting this postgres, but I would like to understand if this is 100% related with bad hardware, or a prolly client problem, hiting against my postgres
red hat linux, 2.4.21, 4 gb of RAM, postgres 7.4.2.
send(9, "D\200\0\0\0\0162002-12-30D\200\0\0\0\0162002-12-30"..., 8192, 0) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
send(9, "D\200\0\0\0\0162002-12-30D\200\0\0\0\0162002-12-30"..., 8192, 0) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
send(9, "D\200\0\0\0\0162002-12-28D\200\0\0\0\0162002-12-28"..., 8192, 0) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
send(9, "D\200\0\0\0\0162002-12-28D\200\0\0\0\0162002-12-28"..., 8192, 0) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
send(9, "D\200\0\0\0\0162002-12-30D\200\0\0\0\0162002-12-30"..., 8192, 0) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
send(9, "D\200\0\0\0\0162002-12-28D\200\0\0\0\0162002-12-28"..., 8192, 0) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
send(9, "D\200\0\0\0\0162002-12-28D\200\0\0\0\0162002-12-28"..., 8192, 0) = -1 EPIPE (Broken pipe)
Thanks in advance.
