Thanks alot john.
that was helpful
On 5/14/07, John D. Burger <[EMAIL PROTECTED]> wrote:
Jasbinder Singh Bali wrote:
> could you please elaborate this concept of queue table?
The basic idea is to for the insert trigger to not explicitly kick
off the work you need to have done, but simply inse
Jasbinder Singh Bali wrote:
could you please elaborate this concept of queue table?
The basic idea is to for the insert trigger to not explicitly kick
off the work you need to have done, but simply insert a row into a
"work request table". A separate process notices that there is a
work
could you please elaborate this concept of queue table?
~Jas
On 5/12/07, Martijn van Oosterhout <[EMAIL PROTECTED]> wrote:
On Fri, May 11, 2007 at 04:07:10PM -0400, Jasbinder Singh Bali wrote:
> I have a transaction in postgres database as follows:
>
> 1 Insert in table xyz
> 2 trigger fired on
On Fri, May 11, 2007 at 04:07:10PM -0400, Jasbinder Singh Bali wrote:
> I have a transaction in postgres database as follows:
>
> 1 Insert in table xyz
> 2 trigger fired on table xyz after insert
> 3 Trigger calls a function func
> 4 func is an implementation of a client socket in perl
>
> 1-4 ha
I have a transaction in postgres database as follows:
1 Insert in table xyz
2 trigger fired on table xyz after insert
3 Trigger calls a function func
4 func is an implementation of a client socket in perl
1-4 happens in database environment only
at 4, a socket connection is opened to a unix too
