pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Will LaShell <will@lashell.net>
To: Marc G. Fournier <scrappy@hub.org>
Cc: PostgreSQL Admin <pgsql-admin@postgresql.org>
Subject: Re: Replication
Date: 28 Jan 2003 16:50:03 -0700
Message-ID: <1043797803.1437.3.camel@lyric.ofsloans.com> (raw)
In-Reply-To: <20030128134750.V22851@hub.org>
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>
	<20030128134750.V22851@hub.org>

On Tue, 2003-01-28 at 11:01, Marc G. Fournier wrote:
> On Tue, 28 Jan 2003, Will LaShell wrote:
> 
> > Hrmm, this is kind of sad. rserv actually does work pretty well. We use
> > it in a production environment here at OFS on a medium size database
> > cluster.
> 
> I think you are the first person taht I've seen that has admit'd to using
> it ... other then a few 'build related' issues, I've never seen anyone do
> anything with it ...

Odd, for a lot of uses at least up to pg version 7.2 it just works well.

> > The biggest issue we had was when we created replication id's to use was
> > that we used bigint field type for the id. Which as we all know suck
> > rocks to use in postgres. Once we specifically cast the field to let it
> > use the index the whole thing just magically worked nice and fast. Note
> > that it did work before it just worked a whole lot slower.
> >
> > What problems have been reported with 7.3?
> 
> The biggest one I've heard: documentation sucks

This truely is an issue, the documentation can be painful, however in
reality there is very little to do with it. Run the master / slave setup
add the tables,  and run the replicate.  I think perhaps the greatest
documentation work could be done in terms of setup examples, and more
explanation of the arguments to the various scripts.

> > Additionally, aren't the eRserver maintainers in theory releasing
> > updates to rserv every year or so? ( At least that's what has been said
> > in the past. )
> 
> Actually, eRServer right now is nowhere near what you are using right now
> ... over the past few months, its been re-written in Java and is now
> multi-slave ... I got my first "live" experience with it this past
> weekend (I did alot of work on the new perl scripts for administrative,
> but never had time to actually get it live) ... we used PgMarket as a
> 'test' case for a demo, and setup consisted of:
> 
> ./ers_setup <args> (sets up master and initial slave)
> 
> and a foreach loop based on a psql -l on the database to run:
> 
> ./ers_addtable <tablename>
> 
> The servers were configured so that if you pull'd the plug out of the
> master server, everything auto-fail'd over to the slave, so that it was
> transparent to anyone hitting the site ... we even had the web servers
> themselves in a failover state ...
>
This is excellent! Now the real question is when will we see this type
of functionality released back into the community, or will there be no
future updates of rserv at all? Or?

Sincerely,

Will LaShell

Attachments:

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

view thread (63+ messages)  latest in thread

Message-ID: <1043797803.1437.3.camel@lyric.ofsloans.com>
Permalink:  ../1043797803.1437.3.camel@lyric.ofsloans.com/
Also on:    postgresql.org/message-id/1043797803.1437.3.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, scrappy@hub.org
  Subject: Re: Replication
  In-Reply-To: <1043797803.1437.3.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> <20030128134750.V22851@hub.org> <1043797803.1437.3.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