pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-performance@postgresql.org
Subject: Re: Replication
Date: Wed, 20 Jun 2007 11:06:46 -0400
Message-ID: <20070620150646.GP31426@phlogiston.dyndns.org> (raw)
In-Reply-To: <4676D4F6.1020508@bluegap.ch>
References: <4671CBBA.6010104@emolecules.com>
	<4671CDB1.3090708@commandprompt.com>
	<4676C3A9.7070703@bluegap.ch>
	<4676CFCB.5070505@emolecules.com>
	<4676D4F6.1020508@bluegap.ch>

On Mon, Jun 18, 2007 at 08:54:46PM +0200, Markus Schiltknecht wrote:
> Postgres-R has been the name of the research project by Bettina Kemme et 
> al. Slony-II was the name Neil and Gavin gave their attempt to continue 
> that project.

This isn't quite true.  Slony-II was originally conceived by Jan as
an attempt to implement some of the Postgres-R ideas.  For our uses,
however, Postgres-R had built into it a rather knotty design problem:
under high-contention workloads, it will automatically increase the
number of ROLLBACKs users experience.  Jan had some ideas on how to
solve this by moving around the GC events and doing slightly
different things with them.

To that end, Afilias sponsored a small workshop in Toronto during one
of the coldest weeks the city has ever seen.  This should have been a
clue, perhaps. ;-)  Anyway, the upshot of this was that two or three
different approaches were attempted in prototypes.  AFAIK, Neil and
Gavin got the farthest, but just about everyone who was involved in
the original workshop all independently concluded that the approach
we were attempting to get to work was doomed -- it might go, but
the overhead was great enough that it wouldn't be any benefit. 

Part of the problem, as near as I could tell, was that we had no
group communication protocol that would really work.  Spread needed a
_lot_ of work (where "lot of work" may mean "rewrite"), and I just
didn't have the humans to put on that problem.  Another part of the
problem was that, for high-contention workloads like the ones we
happened to be working on, an optimistic approach like Postgres-R is
probably always going to be a loser.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
In the future this spectacle of the middle classes shocking the avant-
garde will probably become the textbook definition of Postmodernism. 
                --Brad Holland



view thread (22+ messages)  latest in thread

Message-ID: <20070620150646.GP31426@phlogiston.dyndns.org>
Permalink:  ../20070620150646.GP31426@phlogiston.dyndns.org/
Also on:    postgresql.org/message-id/20070620150646.GP31426@phlogiston.dyndns.org

 · 

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-performance@postgresql.org
  Cc: ajs@crankycanuck.ca
  Subject: Re: Replication
  In-Reply-To: <20070620150646.GP31426@phlogiston.dyndns.org>

* 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