Re: Trigger that spawns forked process
От | Christopher Murtagh |
---|---|
Тема | Re: Trigger that spawns forked process |
Дата | |
Msg-id | 1115669604.7811.4.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: Trigger that spawns forked process (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Trigger that spawns forked process
|
Список | pgsql-general |
On Mon, 2005-05-09 at 15:38 -0400, Tom Lane wrote: > Christopher Murtagh <christopher.murtagh@mcgill.ca> writes: > > I would like to write a trigger or function that spawns a forked > > process so that the transaction is considered 'complete' to the client, > > but continues to perform more work. > > It's not very clear what you are hoping to have the forked process do, > but if it's supposed to be another backend, forget it --- won't work. No, I don't want the trigger to do any db stuff at all. Basically, I've got a content management system that is going to be split across a cluster. Upon an update submission from one of them, I want to replicate across the others (which can happen in pseudo real time). So, basically the DB is the master, once it makes an update, it will spawn a process to the syncronization (all of this code is written). I just don't want the initial update process to wait for replication to finish (which is only a second or two under normal load). I could write a daemon that would sit an listen to these replication requests, but that just seems to be more complex than I need. Cheers, Chris -- Christopher Murtagh Enterprise Systems Administrator ISR / Web Service Group McGill University Montreal, Quebec Canada Tel.: (514) 398-3122 Fax: (514) 398-2017
В списке pgsql-general по дате отправления: