Search Postgresql Archives

Concurrency question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I'm trying to figure out the best way to handle the following situation.

There are two processes, A, and B.

A is a daemon process that performs a select, and then slowly iterates
over the results, performing updates along the way.

It is possible that interactive process B comes along, and wants to
change the data that A is working with.  B should not 1) hang or 2)
fail (it's interactive, and in this case the user is always right). 
It's not optimal, but it would be ok if A failed - indeed, it would be
better than if it kept working with the (now incorrect) data that it
pulled from the select prior to the user's intervention.

Thoughts?

Thankyou for any insight you can send my way!
--
David N. Welton
 - http://www.dedasys.com/davidw/

Linux, Open Source Consulting
 - http://www.dedasys.com/


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux