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 54511A7E.8060703@BlueTreble.com
Whole thread Raw
In response to Re: Proposal: Log inability to lock pages during vacuum  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposal: Log inability to lock pages during vacuum
List pgsql-hackers
On 10/21/14, 6:05 PM, Tom Lane wrote:
> Jim Nasby <Jim.Nasby@BlueTreble.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



pgsql-hackers by date:

Previous
From: Jeremy Harris
Date:
Subject: Re: Directory/File Access Permissions for COPY and Generic File Access Functions
Next
From: Kirk Roybal
Date:
Subject: Re: lag_until_you_get_something() OVER () window function