Re: Database Insertion commitment

On mán, 2007-07-09 at 05:22 -0400, Jasbinder Singh Bali wrote:

>
> The only difference between you test case my a sample test case that I
> would provide is the Perform part in the trigger function.
>
> In my program Perform part is about opening a socket connection with a
> Unix Tools server that runs traceroute and populates records in  table
> test.

then the inserts into table test are made in a separate transaction.


>
> One reason I see that new insert does't see the values of old insert
> is because as soon as socket connection is established, my trigger
> returns and 1st insert is complete even though I'm not sure whether
> the unix tools server has already inserted values in table test or
> not. There might be a time lag based on how fast traceroute returns,
> though right now its very fast.

you should be able to see the row if the tools server has
committed before the next trigger fires

gnari

>