Skip site navigation (1) Skip section navigation (2)

Re: crash-safe visibility map, take three

From: Rob Wultsch <wultsch(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: crash-safe visibility map, take three
Date: 2010-11-30 13:18:12
Message-ID: AANLkTinQeiV9HhkFDOUB=uewdNR4TryOLBieJ3x28PAD@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, Nov 29, 2010 at 9:57 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> 1. Pin each visibility map page.  If any VM_BECOMING_ALL_VISIBLE bits
> are set, take the exclusive content lock for long enough to clear
> them.

I wonder what the performance hit will be to workloads with contention
and if this feature should be optional.

-- 
Rob Wultsch
wultsch(at)gmail(dot)com

In response to

pgsql-hackers by date

Next:From: Rob WultschDate: 2010-11-30 13:26:37
Subject: Re: DELETE with LIMIT (or my first hack)
Previous:From: Simon RiggsDate: 2010-11-30 12:26:57
Subject: Re: [GENERAL] column-level update privs + lock table

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group