On Jul 18, 2007, at 11:30 AM, Michael Dengler wrote:
Hmm..I was hoping to avoid personal insults....
Anyway, Nuts or not...what I am attempting is to simply have row
from one table inserted into another servers DB I don't see it as
replication because:
a) The destination table will have a trigger that modifies the
arriving data to fit its table scheme.
b) It is not critical that the data be synchronous (ie a lost row
on the destination DB is not a big deal)
c) I see as more of a provision of data to the destination DB NOT A
REPLICATION OF DATA.
Essentially the remote server just wants to know when some record
arrives at the source server and wants to know some of the info
contained in the new record.
And yes it may be that I know little about the myriad of problems
involved with replication...but I do know how to carry on a civil,
adult conversation....maybe we can have a knowledge exchange.
Cheers
Mike
Mike,
If all you need is for your trigger to make a simple query on another
db then you can use dblink or an untrusted version of one of the
available procedural languages such as plperlu or plpythonu.
Erik Jones
Software Developer | Emma®
[EMAIL PROTECTED]
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
