From: | "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com> |
---|---|
To: | "Keaton Adams" <kadams(at)mxlogic(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL Replication with read-only access to standby DB |
Date: | 2008-03-25 20:18:16 |
Message-ID: | 396486430803251318qec05a7bt709c22d3ae69af39@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Tue, Mar 25, 2008 at 1:11 PM, Keaton Adams <kadams(at)mxlogic(dot)com> wrote:
> Our organization is looking for a hot-standby option for PostgreSQL that
> uses the WAL (transaction) data to keep the standby current and also allows
> the standby to be read-only accessible for reporting. We have implemented
> WAL shipping through a set of scripts we developed and that works well to
> have a standby DB on the ready in case we need to fail over, but we are
> looking to increase the value of the standby server by making it available
> for queries. Because of the complexities of our environment using a
> table/trigger based replication method such as Slony won't work well.
>
> It would be great if there was a solution (Open Source or Commercial) that
> worked in a similar manner as Oracle Active Data Guard:
>
> Does anyone know of such a solution for PostgreSQL?
I think this does what you want.
http://commandprompt.com/products/mammothreplicator/
--
Regards,
Richard Broersma Jr.
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Broersma | 2008-03-25 20:26:46 | Re: PostgreSQL Replication with read-only access to standby DB |
Previous Message | salman | 2008-03-25 20:17:32 | Re: PostgreSQL Replication with read-only access to standby DB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-03-25 20:21:37 | Re: libpq type system 0.9a |
Previous Message | salman | 2008-03-25 20:17:32 | Re: PostgreSQL Replication with read-only access to standby DB |