Re: Proposal: Log inability to lock pages during vacuum

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-10-29 16:49:02
Message-ID: 54511A7E.8060703@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/21/14, 6:05 PM, Tom Lane wrote:
> Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
>> - What happens if we run out of space to remember skipped blocks?
>
> You forget some, and are no worse off than today. (This might be an
> event worthy of logging, if the array is large enough that we don't
> expect it to happen often ...)

Makes sense. I'll see if there's some reasonable way to retry pages when the array fills up.

I'll make the array 2k in size; that allows for 512 pages without spending a bunch of memory.
--
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-10-29 16:49:12 Re: foreign data wrapper option manipulation during Create foreign table time?
Previous Message Robert Haas 2014-10-29 16:46:55 Re: Failback to old master