Re: replication
От | Adam Lang |
---|---|
Тема | Re: replication |
Дата | |
Msg-id | 002701c023f3$4cb613c0$330a0a0a@Adam обсуждение исходный текст |
Ответ на | Re: replication (Stephan Szabo <sszabo@megazone23.bigpanda.com>) |
Ответы |
RE: replication
|
Список | pgsql-general |
Well, if I end up needing to do something with it, I'll get back to the list on ideas/solutions I encountered and see about potential pitfalls. Adam Lang Systems Engineer Rutgers Casualty Insurance Company ----- Original Message ----- From: "Stephan Szabo" <sszabo@megazone23.bigpanda.com> To: "Daryl Chance" <dchance@valuedata.net> Cc: <pgsql-general@postgresql.org> Sent: Thursday, September 21, 2000 12:59 PM Subject: Re: [GENERAL] replication > On Thu, 21 Sep 2000, Daryl Chance wrote: > > > Could this possibly be done using triggers? I'm new to > > postgres, but I know on a project I was doing using oracle > > the dba could setup triggers to run on the OnInsert() (not > > sure what it's actually called in oracle...). Do maybe > > on the "OnInsert" of table foo you could do: > > > > Insert into foo@remotesite1 .... > > > > Is this possible in postgres? I'm looking at using postgres > > for the next version of my SW and if replication isn't in, > > I'm gonna need something like this :). > > You could probably write a C trigger that would propogate > changes, except that there are still problems. What do you > do when you roll back the transaction? Currently, there > aren't triggers for transaction start and end. Triggers that > do stuff outside the database right now are a bad idea unless > you have some other mechanism to determine whether something > was really supposed to be done. It could be done, but isn't > trivial.
В списке pgsql-general по дате отправления: