Re: AutoVacuum starvation from sinval messages

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: AutoVacuum starvation from sinval messages
Date: 2012-11-08 22:24:52
Message-ID: 20832.1352413492@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
>> When the poll() gets EINTR by SIGUSR1 for the invalidation, it
>> restarts at the full timeout (60 seconds in this case) with no
>> accounting for the time already waited.

> Hmm. That seems like a problem, all right, but I don't believe the
> claim that it applies only to the poll() code path. On many platforms
> the select() path would have the same issue.

BTW, doesn't win32_latch.c have the identical problem? I don't see it
updating the timeout after a signal, either.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-11-08 22:40:43 Re: AutoVacuum starvation from sinval messages
Previous Message Tom Lane 2012-11-08 22:16:23 Re: AutoVacuum starvation from sinval messages