Laurent Birtz wrote:
> SELECT hits FROM webpages WHERE url = ...;
> -- client internally computes $newval = $hits + 1
> UPDATE webpages SET hits = $newval WHERE url = ..;
> if (no error)
> break out of loop;
> end loop
I think you should be able to shave some milliseconds off that loop by
using SAVEPOINTs instead of a full-blown transaction for each tuple.
SELECT hits ...
UPDATE webpages SET hits = ...
if (no error)
break inner loop
ROLLBACK TO foo
end inner loop
end outer loop
> However, I am having problem implementing this scheme in C with libpq.
> Transactions can be aborted because a deadlock occurred or another
> transaction already made some changes to the database.
> My question is how exactly do I detect that this occurred?
IIRC you can apply PQresultStatus to the PGresult returned by the UPDATE.
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
In response to
pgsql-general by date
|Next:||From: Gurjeet Singh||Date: 2007-12-26 07:08:12|
|Subject: Re: how to alter an enum type|
|Previous:||From: Usama Dar||Date: 2007-12-25 16:38:18|
|Subject: Re: Restoring 8.0 db to 8.1|