pg.ddx.io  pgsql-students@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Heikki Linnakangas <hlinnakangas@vmware.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Greg Stark <stark@mit.edu>
Cc: Tan Tran <tankimtran@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: GSoC on WAL-logging hash indexes
Date: Fri, 07 Mar 2014 15:59:12 +0200
Message-ID: <5319D0B0.7030908@vmware.com> (raw)
In-Reply-To: <CA+TgmoacpdE5x3epiwtww_jM3SL5gzV-o6XRG6o0q+W7XrfgzQ@mail.gmail.com>
References: <B444B441-397F-4EDA-8A0C-877B9AF7033B@gmail.com>
	<54977A8C-4AF5-4BCC-B021-78E9CA978077@gmail.com>
	<CA+TgmoY4X7VKyC4dAwujuTuBoyxE2qSJF9aybhWZjxXWoc6J8w@mail.gmail.com>
	<CAM-w4HNGN+eyDzZEaZB_XHLfMCGMqZNZ+2GJpty+PdrDEtzeWg@mail.gmail.com>
	<531873E8.6050802@vmware.com>
	<CA+TgmoZ=HQDaynaRyppSXfYyfTUKrCbk7arFT6Hati7seNmHvg@mail.gmail.com>
	<531992AF.2080306@vmware.com>
	<CA+TgmoacpdE5x3epiwtww_jM3SL5gzV-o6XRG6o0q+W7XrfgzQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 03/07/2014 03:48 PM, Robert Haas wrote:
>> >So, there seems to be a few fairly simple and independent improvements to be
>> >made:
>> >
>> >1. Replace the heavy-weight lock with pin & vacuum-lock.
>> >2. Make it crash-safe, by adding WAL-logging
>> >3. Only acquire the exclusive-lock (vacuum-lock after step 1) in VACUUM for
>> >the squeeze phase.
>> >4. Cache the metapage.
>> >
>> >We still don't know if it's going to be any better than B-tree after all
>> >that's done, but the only way to find out is to go ahead and implement it.
> I'm of the opinion that we ought to start by making splits and
> vacuuming more concurrent, and then do that stuff.

Priorities are a matter of opinion, but note that for many applications 
the concurrency of splits and vacuuming is pretty much irrelevant (at 
least after we do bullet point 3 above). Like, if the index is mostly 
read-only, or at least doesn't grow much. You'd still want it to be 
crash-safe (2), and you might care a lot about the performance of scans 
(1 and 4), but if splits and vacuum hold an exclusive lock for a few 
seconds, that's OK if you only need to do it once in a blue moon.

- Heikki


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (36+ messages)  latest in thread

Message-ID: <5319D0B0.7030908@vmware.com>
Permalink:  ../5319D0B0.7030908@vmware.com/
Also on:    postgresql.org/message-id/5319D0B0.7030908@vmware.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-students@postgresql.org
  Cc: hlinnakangas@vmware.com, robertmhaas@gmail.com, stark@mit.edu, tankimtran@gmail.com, pgsql-hackers@postgresql.org
  Subject: Re: GSoC on WAL-logging hash indexes
  In-Reply-To: <5319D0B0.7030908@vmware.com>
  References: <B444B441-397F-4EDA-8A0C-877B9AF7033B@gmail.com> <54977A8C-4AF5-4BCC-B021-78E9CA978077@gmail.com> <CA+TgmoY4X7VKyC4dAwujuTuBoyxE2qSJF9aybhWZjxXWoc6J8w@mail.gmail.com> <CAM-w4HNGN+eyDzZEaZB_XHLfMCGMqZNZ+2GJpty+PdrDEtzeWg@mail.gmail.com> <531873E8.6050802@vmware.com> <CA+TgmoZ=HQDaynaRyppSXfYyfTUKrCbk7arFT6Hati7seNmHvg@mail.gmail.com> <531992AF.2080306@vmware.com> <CA+TgmoacpdE5x3epiwtww_jM3SL5gzV-o6XRG6o0q+W7XrfgzQ@mail.gmail.com> <5319D0B0.7030908@vmware.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox