On Wed, 2007-07-18 at 15:36, Michael Dengler wrote: > Row X is inserted into TableX in DB1 on server1....TableX trigger > function fires and contacts DB2 on server2 and inserts the row into > TableY on server2.
This kind of problem is usually solved more robustly by inserting the "change" into a local table and let the remote server (or some external program) poll that periodically, and make the necessary changes to the remote server. This method does not have the problems Heikki mentions in his reply with disconnections and transaction rollbacks, as the external program/remote server will only see committed transactions and it can apply the accumulated changes after connection is recovered in case of failure, without blocking the activity on the "master". This is also covered in a few past posts on the postgres lists (I guess you should look in the "general" list for that), in particular you could be interested in the possibility of notifications if you want your poller to be notified immediately when a change occurs. Cheers, Csaba. ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
