Skip site navigation (1) Skip section navigation (2)

Re: [patch] helps fe-connect.c handle -EINTR more gracefully

From: David Ford <david(at)blue-labs(dot)org>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [patch] helps fe-connect.c handle -EINTR more gracefully
Date: 2001-10-29 20:01:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:

>My quibble with David has been about whether the fix is correct in
>detail, not about whether its purpose is correct.

My preference is to spin until ! EINTR as soon as possible after the 
socket operation.  I'm going to seek some advice from kernel people 
regarding the inner workings of sockets.  I suspect that we'll be able 
to get away with handling it like as is done with EINPROGRESS, but 
something is nagging me at the back of my head.

In regards to the other signals, I think there is another subtle 
problem.  Remember a month ago when I had a huge database that I had to 
upgrade, I had no disk space to export it to and when the old version of 
psql ran out of memory it crashed?  The backend continued to push query 
data out the closed pipe until the backend was forcibly closed or the 
query completed.  Naturally this  caused considerable spammage on the 

So I suspect some tuning needs to be done in respect to SIGPIPE w/ the 


In response to


pgsql-hackers by date

Next:From: Serguei MokhovDate: 2001-10-29 20:06:13
Subject: Re: Best way for Postrgesql to pass info to java and back again? (PL/Java)
Previous:From: Serguei MokhovDate: 2001-10-29 19:48:06
Subject: Re: Cross Database Links

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group