From: | Jorge Godoy <jgodoy(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Suggestions for Remote Procedure Calls from PG, please? |
Date: | 2007-10-18 09:07:07 |
Message-ID: | 200710180707.08422.jgodoy@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Em Thursday 18 October 2007 01:44:33 Bret Schuhmacher escreveu:
>
> Thanks for the reply, Tom. I was thinking I could have my remote
> process send a message back to PG via XMLBlaster, too. XMLBlaster is
> a MOM-like message-queuing app that guarantees delivery to
> subscribers. (www.xmlblaster.org) The problem, as you stated,
> though, is transactional integrity :-(. Hmmm, I'll see about the
> to-do queue idea.
You can try implementing a queue, Bret. Make it a FIFO queue and poll from it
regularly. Ten make your transaction insert a record on that queue and take
your action based on that.
A table as simple as:
id SERIAL, -- you can have a routine to reset this when empty
table TEXT, -- includes schema
primary_key TEXT -- to allow for numeric and text PKs
would allow you to retrieve the row that has been changed and take your action
based on that.
--
Jorge Godoy <jgodoy(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | jehan.procaccia | 2007-10-18 09:23:02 | Re: move databases files location |
Previous Message | postgresql.*.thewild | 2007-10-18 07:06:17 | Re: dblink and hostname resolution problem |