| From: | Ian Turner <vectro(at)pipeline(dot)com> |
|---|---|
| To: | Erich <hh(at)cyberpass(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Replication options in Postgres |
| Date: | 2000-08-01 02:17:30 |
| Message-ID: | Pine.LNX.4.21.0007311916230.12874-100000@crafter.house |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> 1. In my PHP code, I have functions like
> inserttransaction(values...). I could just modify inserttransaction()
> so that it runs the same query (the INSERT) on two or more DB
> servers. This would probably work ok.
Why not have a proxy server that your clients talk to, which replicates
the transaction across the other (independent) backend servers, and only
returns OK if all the backends return OK.
Then, theoretically, your databases should always remain concurrant. You
could dump & diff them periodically to make sure.
Ian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5hjM7fn9ub9ZE1xoRAtevAJ9v7Ik/wtasCyTgeCx+zsYvYQWL4QCgubgx
PE0m/X6VoY7+ESZS/p3CIlQ=
=b6Bv
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2000-08-01 03:06:51 | Re: pg_dump & performance degradation |
| Previous Message | K Parker | 2000-08-01 02:10:35 | Openlink ODBC drivers for Unix |