Re: Proposal: Log inability to lock pages during vacuum

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Greg Stark <stark(at)mit(dot)edu>, Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: Log inability to lock pages during vacuum
Date: 2014-11-10 17:09:08
Message-ID: 5460F134.2000002@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/7/14, 8:21 PM, Robert Haas wrote:
> On Thu, Nov 6, 2014 at 8:03 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
>> The problem right now is there's no way to actually obtain evidence that
>> this is (or isn't) something to worry about, because we just silently skip
>> pages. If we had any kind of tracking on this we could stop guessing. :(
>
> I could see logging it, but I agree with Andres and Alvaro that the
> odds are strongly against there being any actual problem here.
>

I'm fine with that. Any other objections? Andres?
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-11-10 17:10:49 Re: pg_background (and more parallelism infrastructure patches)
Previous Message Steve Singer 2014-11-10 16:58:12 Re: tracking commit timestamps