On Tue, Nov 2, 2010 at 5:47 AM, RP Khare <passionate_programmer@xxxxxxxxxxx> wrote: > I want to know how we can handle this issue in PostgreSQL. > When you load your 50,000 record batch, do it inside a transaction block and "SELECT FOR UPDATE" the rows instead of plain "SELECT". That will lock those rows from being updated by other transactions, which will just wait for your transaction to finish, and conversely, your transaction will not proceed until the other transactions have released their update locks as well. This is the most efficient way you can do locking. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
