Date: Fri, 22 Sep 2000 09:31:02 -0600
From: Bruce Guenter <bruceg@em.ca>
To: pgsql-general@postgresql.org
Subject: Re: replication
Message-ID: <20000922093102.A1715@em.ca>
References: <001d01c023ca$e37d9cc0$330a0a0a@Adam>
 <39CB1120.DBEC91AB@haneke.de>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99"
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <39CB1120.DBEC91AB@haneke.de>;
	from elmar@haneke.de on Fri, Sep 22, 2000 at 09:58:24AM +0200


--5vNYLRcllDrimb99
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 22, 2000 at 09:58:24AM +0200, Elmar Haneke wrote:
> Adam Lang wrote:
> > Are there any type of replication features in postgresql 7.0?

I've been thinking that one way to emulate replication would be to run a
pgsql "shim" that would redirect queries to two back-ends
simultaneously, creating transactions for update commands, and aborting
when necessary.  The shim would be a long-running gateway process, that
could check for data consistency when it started up.  This is all off
the top of my head, so is this at all a reasonable idea?

I am running into a similar situation, where I want to set up two live
redundant sites, where nightly updates aren't an option.
--=20
Bruce Guenter <bruceg@em.ca>                       http://em.ca/~bruceg/

--5vNYLRcllDrimb99
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE5y3s26W+y3GmZgOgRAlTZAJwOmm3QnzPLYIbqrQ4t4bS96m1MPwCggO/H
o9j2wlOu3122C/tuu5K86Zc=
=/hb6
-----END PGP SIGNATURE-----

--5vNYLRcllDrimb99--