7.0.2 backend churning out messages
I am having a problem with the zillions of:
pq_flush: send() failed: Broken pipe
FATAL: pq_endmessage failed: errno=32
messages being generated.
What causes this?
How can it be prevented?
-km
"Kurt Miller" <medixcon@pacbell.net> writes:
I am having a problem with the zillions of:
pq_flush: send() failed: Broken pipe
Clients disconnecting prematurely, perhaps?
regards, tom lane
Is there any way to prevent this? It seems if I have one client
disconnecting prematurely it can bring the whole system to its knees.
Please correct me if I'm wrong. Is this also the same for 7.1?
thanks, kurt miller
"Tom Lane" <tgl@sss.pgh.pa.us> wrote in message
news:22557.989723432@sss.pgh.pa.us...
Show quoted text
"Kurt Miller" <medixcon@pacbell.net> writes:
I am having a problem with the zillions of:
pq_flush: send() failed: Broken pipeClients disconnecting prematurely, perhaps?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
"Kurt Miller" <medixcon@pacbell.net> writes:
Is there any way to prevent this? It seems if I have one client
disconnecting prematurely it can bring the whole system to its knees.
To its knees? The "broken pipe" messages themselves are completely
harmless. If you're seeing operational difficulties other than the
appearance of those log messages, then you need to be more specific
about your problem.
regards, tom lane