pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Will LaShell <will@lashell.net>
To: Andrew Sullivan <andrew@libertyrms.info>
Cc: PostgreSQL Admin <pgsql-admin@postgresql.org>
Subject: Re: Replication
Date: 28 Jan 2003 16:56:25 -0700
Message-ID: <1043798186.1437.11.camel@lyric.ofsloans.com> (raw)
In-Reply-To: <20030128161232.P22543@mail.libertyrms.com>
References: <20030123135353.E4693@mail.libertyrms.com>
	<b13ub4$2o3q$1@news.hub.org>
	<20030127181820.C9007@mail.libertyrms.com>
	<20030128000736.X22851@hub.org>
	<1043773193.6521.7.camel@lyric.ofsloans.com>
	<20030128161232.P22543@mail.libertyrms.com>

On Tue, 2003-01-28 at 14:12, Andrew Sullivan wrote:
> On Tue, Jan 28, 2003 at 09:59:52AM -0700, Will LaShell wrote:
> > What problems have people been having getting rserv to work at all?
> 
> In 2001 I tested it for our anticipated load.  It worked for me, but
> it was not up to the kind of load that we were anticipating.  It was
> reasonable, however, and I was not able to break it; it just wasn't
> up to the load I had to plan for.  We also needed multi-salve
> replication.  We therefore did some work with PostgreSQL, Inc. to
> produce a new, somewhat better version of rserv.  That's what we
> still use in our production systems.
> 
> So I have not had problems getting rserv to work, but it wasn't
> enough for us.  I wouldn't hesitate to recommend it to others,
> though: the strategy is sound, and if it meets your needs, it'll
> probably do fine (assuming it still works with 7.3; when I was
> testing, remember, 7.1.x was the released version).  I seem to recall
> keeping it busy with several hundred transactions per minute, but
> whether that was sustainable I don't know.
> 
> A

I definitely agree with this analysis.  The biggest thing with getting
rserv to work fast, is using the right replication field id. We elected
to use a bigint, created an index only on it and treat it special. If I
get inspired I could post up some performance metrics if anyone cares to
be interested.

I have looked at eRserv in the past, the problem is the price. It's just
a bit high to convince the people here to use. Hopefully I can get them
to change their minds.

Sincerely,

Will LaShell

Attachments:

  signature.asc (application/pgp-signature, 188B) download

view thread (63+ messages)  latest in thread

Message-ID: <1043798186.1437.11.camel@lyric.ofsloans.com>
Permalink:  ../1043798186.1437.11.camel@lyric.ofsloans.com/
Also on:    postgresql.org/message-id/1043798186.1437.11.camel@lyric.ofsloans.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-admin@postgresql.org
  Cc: will@lashell.net, andrew@libertyrms.info
  Subject: Re: Replication
  In-Reply-To: <1043798186.1437.11.camel@lyric.ofsloans.com>
  References: <20030123135353.E4693@mail.libertyrms.com> <b13ub4$2o3q$1@news.hub.org> <20030127181820.C9007@mail.libertyrms.com> <20030128000736.X22851@hub.org> <1043773193.6521.7.camel@lyric.ofsloans.com> <20030128161232.P22543@mail.libertyrms.com> <1043798186.1437.11.camel@lyric.ofsloans.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