Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 95461479BF1 for ; Tue, 28 Jan 2003 20:42:23 -0500 (EST) Received: from isis.pcis.net (cr.pcis.net [207.18.226.3]) by postgresql.org (Postfix) with ESMTP id 017A5479D48 for ; Tue, 28 Jan 2003 18:54:23 -0500 (EST) Received: from lyric.ofsloans.com (unverified [209.180.142.225]) by isis.pcis.net (Rockliffe SMTPRA 4.5.6) with ESMTP id ; Tue, 28 Jan 2003 17:54:26 -0600 Subject: Re: Replication From: Will LaShell To: Andrew Sullivan Cc: PostgreSQL Admin In-Reply-To: <20030128161232.P22543@mail.libertyrms.com> References: <20030123135353.E4693@mail.libertyrms.com> <20030127181820.C9007@mail.libertyrms.com> <20030128000736.X22851@hub.org> <1043773193.6521.7.camel@lyric.ofsloans.com> <20030128161232.P22543@mail.libertyrms.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-2quJ2kNcNhh766mKkrb3" X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 28 Jan 2003 16:56:25 -0700 Message-Id: <1043798186.1437.11.camel@lyric.ofsloans.com> Mime-Version: 1.0 X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/322 X-Sequence-Number: 7164 --=-2quJ2kNcNhh766mKkrb3 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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? >=20 > 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. >=20 > 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. >=20 > 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 --=-2quJ2kNcNhh766mKkrb3 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQA+NxipZr3R5kgOZd0RArqIAJ9apR/ZqkhPKqjQVw/Aa6jI91bbBgCdGXYl Gfrv1cxi0LFivI+geFd7oe0= =EMkk -----END PGP SIGNATURE----- --=-2quJ2kNcNhh766mKkrb3--