I have a problem I am trying to solve. I have a rather large
application that uses Postgresql. For performance reasons I
would like to run it on multiple machines. I ran into a problem
that I am trying to solve and the easiest solution seems to
involve using table/record locking in Postgresql.

What I need to do is simulate "critical sections" across these
multiple machines. I was thinking that I could construct a table
and set it up to do either record or table locking. Will this
cause the Postgresql server to hold off the other "applications"
so long as one of them is already using the record?

Thanks in advance,
Chance