Re: AutoVacuum starvation from sinval messages

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: AutoVacuum starvation from sinval messages
Date: 2012-11-09 14:32:15
Message-ID: CA+U5nMLDhDeBvXBbdOLCxzAqtuW6mfTr_Ws3S8Qidk10aVFaoA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9 November 2012 14:16, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Nov 9, 2012 at 9:02 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>>> So, do we need a sinval overrun or just a sinval message to provoke
>>> starvation? The former would be bad but the latter would be really,
>>> really bad. IIRC the queue has 4K entries, and IIRC a single DDL
>>> operation might provoke a couple of sinvals, but I'm thinking that
>>> somebody would probably have to be creating >1024 temp tables a minute
>>> to overrun the queue, which is very possible but not necessarily
>>> common. OTOH, creating 1 temp table a minute would hit a much broader
>>> swath of users.
>>
>> The point is moot because latches don't work that way anymore.
>
> One of us is confused, because IIUC Tom just fixed this this morning,
> and I'm trying to figure out how many users will be affected by it,
> and how seriously. Like, do we need an immediate minor release?

You asked what provokes starvation, and the answer is nothing anymore,
since Tom's commit. No confusion here...

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Wanner 2012-11-09 14:42:58 Re: Enabling Checksums
Previous Message Markus Wanner 2012-11-09 14:31:44 Re: Enabling Checksums