Re: Lock table, Select for update and Serialization error

From: sudhir <sudhirj(at)cse(dot)iitb(dot)ac(dot)in>
To: Joris Dobbelsteen <Joris(at)familiedobbelsteen(dot)nl>
Cc: pgsql-general(at)postgresql(dot)org, Albe Laurenz <all(at)adv(dot)magwien(dot)gv(dot)at>
Subject: Re: Lock table, Select for update and Serialization error
Date: 2007-05-23 04:51:14
Message-ID: 4653C842.8020209@cse.iitb.ac.in
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> Summarizing:
> * Lock table - High-level: executes fast, but concurrency problems.
> Guarentees about future changes.
> Select for update - Low-level, concurrent, ensures data validity and
> indicates its modified shortly.
> Select for share - Low-level, concurrent, ensures data validity.
>
> Hopefully this clears it up a bit.
>
Yeah, it does. Thanks for your help guys.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message PFC 2007-05-23 06:22:24 Re: Using a trigger with an object-relational manager
Previous Message Ben 2007-05-23 03:12:28 Re: Integrity on large sites