Re: Proposal: Log inability to lock pages during vacuum - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Proposal: Log inability to lock pages during vacuum
Date
Msg-id 5460F134.2000002@BlueTreble.com
Whole thread Raw
In response to Re: Proposal: Log inability to lock pages during vacuum  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Proposal: Log inability to lock pages during vacuum  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 11/7/14, 8:21 PM, Robert Haas wrote:
> On Thu, Nov 6, 2014 at 8:03 PM, Jim Nasby <Jim.Nasby@bluetreble.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



pgsql-hackers by date:

Previous
From: Steve Singer
Date:
Subject: Re: tracking commit timestamps
Next
From: Robert Haas
Date:
Subject: Re: pg_background (and more parallelism infrastructure patches)