Re: Standby databases

From: "Artigas, Ricardo Y(dot)" <rya(at)easycall(dot)net(dot)ph>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Standby databases
Date: 2002-03-14 03:08:59
Message-ID: 9C3CCFCE6CBFD3118F1100A0C999693201463D6A@MIS
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Have you checked pgReplicator for replication?

:~)
Ricky Y. Artigas
Database Administrator /
Systems Analyst/Programmer
Information Technology Division
Easycall Communications Phils., Inc.

> -------------------------------
> IMPORTANT NOTICE:

> This message (and any attachment hereto) may contain privileged and/or
> confidential information specific to EasyCall. If you are not the intended
> addressee indicated in this message, you may not copy or disseminate this
> message (or any attachment hereto) to anyone. Instead, please destroy this
> message (and any attachment hereto), and kindly notify the sender by reply
> email. Any information in this message (and any attachment thereto) that
> do not relate to the official business of EasyCall shall be understood as
> neither given nor endorsed by the company.
>
>
> -----Original Message-----
> From: Fernando Lozano [SMTP:fsl(at)centroin(dot)com(dot)br]
> Sent: Thursday, March 14, 2002 9:02 AM
> To: pgsql-general(at)postgresql(dot)org
> Subject: [GENERAL] Standby databases
>
> Hi there!
>
> Is it possible to create hot standby databases using PostgreSQL, that
> is, have one server send its transaction log to another server who
> periodically applies the transactions?
>
>
> []s, Fernando Lozano
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

Browse pgsql-general by date

  From Date Subject
Next Message Steve Lane 2002-03-14 03:35:25 Re: Last Insert
Previous Message Sergio Freue 2002-03-14 03:07:54 Select not using primary key index