| From: | "Kevin Grittner" <kgrittn(at)mail(dot)com> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "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:43:14 |
| Message-ID: | 20121109144314.77880@gmx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> 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...
So for all those end users running production with a build compiled
from HEAD after Tom's commit this morning there is no issue. I'm
wondering about those using something else in production. What does
it take for their autovacuum to be stalled?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-11-09 14:50:36 | Re: AutoVacuum starvation from sinval messages |
| Previous Message | Markus Wanner | 2012-11-09 14:42:58 | Re: Enabling Checksums |