| From: | Marinos Yannikos <mjy(at)geizhals(dot)at> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: server crash => libpq poll() hangs forever (Linux) |
| Date: | 2010-06-10 19:41:44 |
| Message-ID: | 4C113FF8.60308@geizhals.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am 09.06.2010 16:37, schrieb Tom Lane:
> Marinos Yannikos<mjy(at)geizhals(dot)at> writes:
>> It seems that poll() never receives a connection closed notification under Linux
>> (https://lists.linux-foundation.org/pipermail/bugme-new/2003-April/008335.html -
>> very old report,
>
> "very old report" is right. What makes you think that has anything to
> do with modern kernel versions?
Mainly that I have no other explanation for multiple clients hanging on multiple
client machines (all kernel 2.6.18, some were Xen instances, the server uses
2.6.26) in libpq's poll(), for up to 2 days 10 hours after the server crash
(until we found/restarted them). 2.6.18 is probably not "modern", but reliable,
does anyone have more information regarding poll() changes in more recent
kernels? We'll upgrade some boxes and see if anything changes.
Regards,
Marinos
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2010-06-10 20:00:54 | Re: checkpoint spikes |
| Previous Message | Alan Hodgson | 2010-06-10 18:35:31 | Re: pg/linux How much swap relative to physical memory is needed? |