-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We have installed a product called Quasar for accounting needs at our
company, which is back ended by PostgreSQL. It is a requirement that
the database is replicated, real time, to a secondary machine and
PostgreSQL database, in case of failure of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Browne wrote:
>[EMAIL PROTECTED] ("Joshua D. Drake") writes:
>
>>>You are looking for synchronous replication as opposed to async?
>>>
Currently i have Slony working, but am not satisfied with how it
accomplishes replication, or it's in
[EMAIL PROTECTED] ("Joshua D. Drake") writes:
>> You are looking for synchronous replication as opposed to async?
>>
>> >Currently i have Slony working, but am not satisfied with how it
>> >accomplishes replication, or it's interface, and am curious what
>> >others are using to accomplish replicat
> You are looking for synchronous replication as opposed to async?
>
> >Currently i have Slony working, but am not satisfied with how it
> >accomplishes replication, or it's interface, and am curious what
> >others are using to accomplish replication?
There is also Mammoth Replicator:
http://ww
Kirby Ubben wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We have installed a product called Quasar for accounting needs at our
company, which is back ended by PostgreSQL. It is a requirement that
the database is replicated, real time, to a secondary machine and
PostgreSQL database, in
On Fri, Oct 21, 2005 at 11:28:36AM -0500, Kirby Ubben wrote:
> Currently i have Slony working, but am not satisfied with how it
> accomplishes replication, or it's interface, and am curious what
> others are using to accomplish replication?
What do you find unsatisfactory (or, for that matter,
dis
Unfortunately, the only syncronous replication I know of is
http://pgfoundry.org/projects/pgcluster/, which is statement-based. That
means it's got some substantial drawbacks...
On Fri, Oct 21, 2005 at 11:28:36AM -0500, Kirby Ubben wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We have installed a product called Quasar for accounting needs at our
company, which is back ended by PostgreSQL. It is a requirement that
the database is replicated, real time, to a secondary machine and
PostgreSQL database, in case of failure of th