Thread: replication solution
Hi all, we are looking for a solution to create a replicated database to be used as reporting database with same data of production ( we can accept a lag of some minutes). we already have the Point In Time Recovery but we need a solution where the standby is always open in readonly , but the data is replicated continuosly from primary. The Slony solution could be a possibility but the production database is 80 Gb of data with around 10000 transaction each hour. DO you have some suggestion for our implementaiont if exists?? thanks a lot Silvio --- Utilizziamo i dati personali che la riguardano esclusivamente per nostre finalità amministrative e contabili, anche quandoli comunichiamo a terzi. Informazioni dettagliate, anche in ordine al Suo diritto di accesso e agli altri Suoi diritti,sono riportate alla pagina http://www.savinodelbene.com/news/privacy.html Se avete ricevuto questo messaggio per errore Vi preghiamo di ritornarlo al mittente eliminandolo assieme agli eventualiallegati, ai sensi art. 616 codice penale http://www.savinodelbene.com/codice_penale_616.html L'Azienda non si assume alcuna responsabilità giuridica qualora pervengano da questo indirizzo messaggi estranei all'attivitàlavorativa o contrari a norme. --
Silvio Brandani <silvio.brandani@tech.sdb.it> wrote: > we already have the Point In Time Recovery but we need a solution > where the standby is always open in readonly , but the data is > replicated continuosly from primary. What's your time frame? The Hot Standby and Streaming Replication features in PostgreSQL 9.0 will do exactly that. 9.0 is currently in beta testing and expected to be released next month. These new features are based on PITR techniques, but SR allows the WAL data to flow across a connection in near real-time, and HS allows the standby to be used for read-only queries. -Kevin
Hi, 24.Ağu.2010 tarihinde 16:46 saatinde, Silvio Brandani <silvio.brandani@tech.sdb.i t> şunları yazdı: > The Slony solution could be a possibility but the production > database is 80 Gb of data with around 10000 transaction each hour. We do at least 15x more transactions with Slony, w/o any issues. Slony should be good for you. -- Devrim GÜNDÜZ PostgreSQL DBA @ Akinon/Markafoni, Red Hat Certified Engineer devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz
On Tue, 2010-08-24 at 15:46 +0200, Silvio Brandani wrote: > Hi all, > > we are looking for a solution to create a replicated database to be used > as reporting database with same data of production ( we can accept a lag > of some minutes). > > we already have the Point In Time Recovery but we need a solution where > the standby is always open in readonly , but the data is replicated > continuosly from primary. > > The Slony solution could be a possibility but the production database is > 80 Gb of data with around 10000 transaction each hour. Slony (or Londiste) can handle that without issue, at all. Joshua D. Drake -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579 Consulting, Training, Support, Custom Development, Engineering http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt
On Tue, Aug 24, 2010 at 10:38 AM, Joshua D. Drake <jd@commandprompt.com> wrote: > On Tue, 2010-08-24 at 15:46 +0200, Silvio Brandani wrote: >> The Slony solution could be a possibility but the production database is >> 80 Gb of data with around 10000 transaction each hour. > Slony (or Londiste) can handle that without issue, at all. Bucardo, too. All three work on similar principles. rls -- :wq
On Tue, 2010-08-24 at 15:46 +0200, Silvio Brandani wrote: > Hi all, > > we are looking for a solution to create a replicated database to be used > as reporting database with same data of production ( we can accept a lag > of some minutes). > > we already have the Point In Time Recovery but we need a solution where > the standby is always open in readonly , but the data is replicated > continuosly from primary. > > The Slony solution could be a possibility but the production database is > 80 Gb of data with around 10000 transaction each hour. Slony (or Londiste) can handle that without issue, at all. Joshua D. Drake -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579 Consulting, Training, Support, Custom Development, Engineering http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt
On Tue, 2010-08-24 at 15:46 +0200, Silvio Brandani wrote: > Hi all, > > we are looking for a solution to create a replicated database to be used > as reporting database with same data of production ( we can accept a lag > of some minutes). > > we already have the Point In Time Recovery but we need a solution where > the standby is always open in readonly , but the data is replicated > continuosly from primary. > > The Slony solution could be a possibility but the production database is > 80 Gb of data with around 10000 transaction each hour. > > DO you have some suggestion for our implementaiont if exists?? PostgreSQL 9.0 is production ready now and supports Hot Standby, which is exactly what you want. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Training and Services
I've heard that rubyrep (http://www.rubyrep.org) is a good tool for replication too. I think it has gained popularity because of its ease of use. On a similar note I am eager to try postgreSQl 9.0 bulit in hot standby solution.I can't really wait till Postgersql rolls out replicated solution which can also be used for a failover. Dinesh On 10/13/2010 1:06 PM, Simon Riggs wrote: > On Tue, 2010-08-24 at 15:46 +0200, Silvio Brandani wrote: >> Hi all, >> >> we are looking for a solution to create a replicated database to be used >> as reporting database with same data of production ( we can accept a lag >> of some minutes). >> >> we already have the Point In Time Recovery but we need a solution where >> the standby is always open in readonly , but the data is replicated >> continuosly from primary. >> >> The Slony solution could be a possibility but the production database is >> 80 Gb of data with around 10000 transaction each hour. >> >> DO you have some suggestion for our implementaiont if exists?? > PostgreSQL 9.0 is production ready now and supports Hot Standby, which > is exactly what you want. >
Simon Riggs ha scritto: > On Tue, 2010-08-24 at 15:46 +0200, Silvio Brandani wrote: > >> Hi all, >> >> we are looking for a solution to create a replicated database to be used >> as reporting database with same data of production ( we can accept a lag >> of some minutes). >> >> we already have the Point In Time Recovery but we need a solution where >> the standby is always open in readonly , but the data is replicated >> continuosly from primary. >> >> The Slony solution could be a possibility but the production database is >> 80 Gb of data with around 10000 transaction each hour. >> >> DO you have some suggestion for our implementaiont if exists?? >> > > PostgreSQL 9.0 is production ready now and supports Hot Standby, which > is exactly what you want. > > We are testing postgres 9.0.1 hot-standby feautures in a dev environment. Thanks a lot Silvio Brandani --- Utilizziamo i dati personali che la riguardano esclusivamente per nostre finalit� amministrative e contabili, anche quandoli comunichiamo a terzi. Informazioni dettagliate, anche in ordine al Suo diritto di accesso e agli altri Suoi diritti,sono riportate alla pagina http://www.savinodelbene.com/privacy.html Se avete ricevuto questo messaggio per errore Vi preghiamo di ritornarlo al mittente eliminandolo assieme agli eventualiallegati, ai sensi art. 616 codice penale http://www.savinodelbene.com/privacy/codice_penale_616.html L'Azienda non si assume alcuna responsabilit� giuridica qualora pervengano da questo indirizzo messaggi estranei all'attivit�lavorativa o contrari a norme. --