Skip site navigation (1) Skip section navigation (2)

Re: Buggy SELEC ... FROM UPDATE ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Patrice Espié <patrice(dot)espie(at)univ-lyon2(dot)fr>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Buggy SELEC ... FROM UPDATE ?
Date: 2001-04-13 17:08:39
Message-ID: 4748.987181719@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-novice
=?iso-8859-1?Q?Patrice_Espi=E9?= <patrice(dot)espie(at)univ-lyon2(dot)fr> writes:
> When a lot of threads (well, I tried 20, 5 and 2) used this algo, more than
> one thread get the syslock %d at the same time.

"Threads"?  Are you sure each thread has an independent database
connection, and you're not reusing connections to issue commands
from different threads?  Your pseudocode looks like it should work
if issued to separate backends ...

			regards, tom lane

In response to

pgsql-novice by date

Next:From: Tom LaneDate: 2001-04-14 01:37:16
Subject: Re: Increasing max connections
Previous:From: Tom LaneDate: 2001-04-13 16:35:44
Subject: Re: Calling 'c' function from PostGreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group