pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dan Ports <drkp@csail.mit.edu>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: SSI bug?
Date: Tue, 1 Mar 2011 15:09:58 -0500
Message-ID: <20110301200957.GA91864@csail.mit.edu> (raw)
In-Reply-To: <4D6D27DE.8080304@enterprisedb.com>
References: <4D616C14020000250003AD9A@gw.wicourts.gov>
	<20110221234236.4635E19D574@mail.netbsd.org>
	<20110222024129.GC74913@csail.mit.edu>
	<4D639519020000250003AE0D@gw.wicourts.gov>
	<20110222232054.GC61128@csail.mit.edu>
	<20110301000306.GL10115@csail.mit.edu>
	<4D6D27DE.8080304@enterprisedb.com>

On Tue, Mar 01, 2011 at 07:07:42PM +0200, Heikki Linnakangas wrote:
> Was there test cases for any of the issues fixed by this patch that we 
> should add to the suite?

Some of these issues are tricky to test, e.g. some of the code about
transferring predicate locks to a new target doesn't get exercised
unless an index page gets split while there are concurrent
transactions holding locks on that page.

I have not been able to find a good way to test these other than
system-level testing using a concurrent workload (usually the DBT-2
benchmark). I'd certainly be open to suggestions!

Dan

-- 
Dan R. K. Ports              MIT CSAIL                http://drkp.net/



view thread (71+ messages)  latest in thread

Message-ID: <20110301200957.GA91864@csail.mit.edu>
Permalink:  ../20110301200957.GA91864@csail.mit.edu/
Also on:    postgresql.org/message-id/20110301200957.GA91864@csail.mit.edu

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: drkp@csail.mit.edu, heikki.linnakangas@enterprisedb.com
  Subject: Re: SSI bug?
  In-Reply-To: <20110301200957.GA91864@csail.mit.edu>

* 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