Re: Replication for a large database - Mailing list pgsql-sql
From | The Hermit Hacker |
---|---|
Subject | Re: Replication for a large database |
Date | |
Msg-id | 20030507222653.T728@hub.org Whole thread Raw |
In response to | Re: Replication for a large database (Michael A Nachbaur <mike@nachbaur.com>) |
List | pgsql-sql |
Postgres-R is not pgsql.com's product ... eRServer is ... the code that is in product has been quite extensively pounded on by both the .org and .info registries ... On Mon, 5 May 2003, Michael A Nachbaur wrote: > IIRC, pgsql.com's product (Postgres-R I think it's called) is based on > PostgreSQL-6.4.2, which won't work for me since I use a lot of features > available only in the 7.x generation. > > I'm using the Rserv code from the contrib section of Postgres, and that's what > I'm having problems with. > > On Monday 05 May 2003 10:30 am, Rajesh Kumar Mallah wrote: > > Have u tried the Rserv solution which pgsql.com provides > > commercially? I have heard its pretty good. > > > > > > regds > > mallah. > > > > On Mon, 5 May 2003, Michael A Nachbaur wrote: > > > Hello all, > > > > > > I apologize if this has already been covered in the past, but I couldn't > > > seem to find an adequate solution to my problem in the archives. > > > > > > I have a database that is used for a bandwidth tracking system at a > > > broadband ISP. To make a long story short, I'm inserting over 800,000 > > > records per day into this database. Suffice to say, the uptime of this > > > database is of paramount importance, so I would like to have a more > > > up-to-date backup copy of my database in the event of a failure (more > > > recent than my twice-per-day db_dump backup). > > > > > > I have two servers, both Dual Xeon-2G with 4G of RAM, and would like to > > > replicate between the two. I would like to have "live" replication, but > > > I couldn't seem to find a solution for that for PostgreSQL. I tried > > > RServ but, after attempting it, I saw a mailing list posting saying that > > > it is more-or-less useless for databases that have a large number of > > > inserts (like mine). > > > > > > When I perform a replication after a batch of data is inserted, the query > > > runs literally for hours before it returns. I have never actually been > > > present during the whole replication duration since it takes longer than > > > my 8-12 hour days here at work. > > > > > > Is there any replication solution that would fit my needs? I'm taking > > > advantage of some PG7.2 features so "downgrading" to the 6.x version of > > > postgres that has replication support isn't an option. > > > > > > Thanks. > > > > > > --man > > > > > > > > > ---------------------------(end of broadcast)--------------------------- > > > TIP 4: Don't 'kill -9' the postmaster > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org