From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Thalis A(dot) Kalfigopoulos" <thalis(at)cs(dot)pitt(dot)edu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Multiple pq_flush: send() failed: Broken pipe |
Date: | 2001-06-13 16:35:13 |
Message-ID: | 26962.992450113@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Thalis A. Kalfigopoulos" <thalis(at)cs(dot)pitt(dot)edu> writes:
> I have my logfile flooded with the message:
> pq_flush: send() failed: Broken pipe
> I went through the archives and I found plenty of (older) cases where
> this was usually accompanied by a 'FATAL:' message and lead to a
> crash. In my case there is only this by itself (*many* times) and it
> doesn't lead to a crash. Any idea what could be causing it?
Perhaps some backend churning away on a SELECT that produces gigabytes
of output? (Not hard to do with a careless unqualified join ...)
The client might have long since given up and disconnected, but right
now the backend won't notice until it finishes the query.
Send a SIGINT to the errant backend to get it to cancel the query.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Brent R. Matzelle | 2001-06-13 16:38:31 | SQL Load Balancer for PostgreSQL |
Previous Message | Tom Lane | 2001-06-13 16:33:03 | Re: pg_dump problem |