| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Brar Piening <lists(at)piening(dot)info>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Some 9.5beta2 backend processes not terminating properly? |
| Date: | 2016-01-04 15:27:54 |
| Message-ID: | 20160104152754.GA28025@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-01-04 10:20:43 -0500, Tom Lane wrote:
> I'm slightly worried about breaking 3rd-party code that might be using
> recv() and somehow expecting the current behavior. However, it's equally
> arguable that such code would have Windows-specific problems that would be
> fixed by the patch.
I don't really see how somebody could validly depend on the old
behaviour, given it always was windows only, and there only with
nonblocking sockets. Seems more likely to be an undiscovered bug for
such a hyptothetical user.
I also think there's rather few drivers / clients actually shutting down
sockets. Here it AFAICS really was a more or less unintentional side
effect.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-01-04 15:30:28 | Re: Avoiding pin scan during btree vacuum |
| Previous Message | Magnus Hagander | 2016-01-04 15:22:34 | Re: Some 9.5beta2 backend processes not terminating properly? |