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

From Robert Haas
Subject Re: Proposal: Log inability to lock pages during vacuum
Date
Msg-id CA+TgmoZfMgJSWoP_SPRdZMyswTudTLU-pWzRUAw26JnLwLiD9g@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: Log inability to lock pages during vacuum  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Proposal: Log inability to lock pages during vacuum  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: BRIN indexes - TRAP: BadArgument
Next
From: Robert Haas
Date:
Subject: Re: Add CREATE support to event triggers