From: | "Simon Windsor" <simon(dot)windsor(at)cornfield(dot)org(dot)uk> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Replication options |
Date: | 2004-02-19 18:24:26 |
Message-ID: | E1AtsnE-0000Hj-00@gaul.cornfield.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi
I am used to using Oracle (15 years) and MySQL(5 years), but I am planning
to move an existing application from MySQL to Postgres. The reasons are very
simple,
* New requirements means we need views, or a significant re-write
* Better query/index performance essential.
* Postgres and MySQL share a very common implementation of SQL-92, and
what is missing can easily be implanted in functions
The only negative issue is replication. I have checked several Postgres
Replication options and unsure which way to go. Can anyone recommend a
replication option that meets the following:
* Does not use triggers. Usually slow, and one action that modifies
several records, can trigger many actions on slaves/peers.
* Does use WAL, or other log, so that SQL DDL/DML is copied to
slave/peer, rather than the result of the DDL/DML.
* Must provide master-master and master-slave replication
* Simple to configure and maintain
Many Thanx
Simon Windsor
Eml: simon(dot)windsor(at)cornfield(dot)org(dot)uk
Tel: 01454 617689
Mob: 07960 321599
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Mailscanner thanks transtec Computers for their support.
From | Date | Subject | |
---|---|---|---|
Next Message | Al Hulaton | 2004-02-19 18:28:43 | Re: book for postgresql |
Previous Message | Randall Skelton | 2004-02-19 18:23:34 | Re: Inner join question |