Re: Question: update and transaction isolation - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Question: update and transaction isolation
Date
Msg-id Pine.LNX.4.30.0204031232170.684-100000@peter.localdomain
Whole thread Raw
In response to Re: Question: update and transaction isolation  (mlw <markw@mohawksoft.com>)
Responses Re: Question: update and transaction isolation  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
List pgsql-hackers
mlw writes:

> For each page hit, I do this:
>
> update pagecounts set counter = counter + 1 where pagename = 'testpag.php'
>
> Do I have to set a particular isolation level? Or does this not work in
> general?

In read committed level, if the second update launches before the first
update is finished (commits), then both of these updates will operate on
the old counter value.  That is, you miss one page hit.

If it's possible, you might want to consider "logging" your page hits and
make a view for the page counts (with group by, etc.).  That will get you
around the concurrency issues altogether.

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Suggestions please: names for function cachability
Next
From: Tom Lane
Date:
Subject: Re: Suggestions please: names for function cachabilityattributes