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 quando li 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 eventuali allegati, 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.
--

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Silvio Brandani <silvio.brandani [at] 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

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Hi,

24.A=C4=9Fu.2010 tarihinde 16:46 saatinde, Silvio Brandani <silvio.brandani=
[at] tech.sdb.i
t> =C5=9Funlar=C4=B1 yazd=C4=B1:

> 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=C3=9CND=C3=9CZ
PostgreSQL DBA [at] 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
--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

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


--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin