From: | "Alvin Hung" <alvin_hung(at)hotmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Using PGSQL to help coordinate many servers |
Date: | 2003-02-26 10:45:32 |
Message-ID: | F1081goaKX0B5qpwpK800008b0b@hotmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
We have a need to coordinate multiple app-servers that are using the same
database. Basically, we are thinking about using a table row as the
coordination mechanism. When an app-server needs to perform an action that
must be exclusive, it will try to lock that table row first. It will wait on
that lock if someone else has it.
Has anyone done something like this before? What's the performance and
resource usage like if the exclusive action is pretty short? Does PGSQL do
FIFO when multiple connections wait on the same lock?
BTW we are using JDBC to connect to the server.
Thanks for your help.
_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8.
http://join.msn.com/?page=features/junkmail
From | Date | Subject | |
---|---|---|---|
Next Message | Hervé Piedvache | 2003-02-26 10:55:51 | Re: 7.4? |
Previous Message | Mark Cave-Ayland | 2003-02-26 10:41:52 | Re: Join query crashes 7.3.1 backend... |