Date: Thu, 24 Aug 2006 16:52:55 -0400
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: Lock Problem
Message-ID: <20060824205255.GA24499@phlogiston.dyndns.org>
References: <3FFA1818C1550246933DEA311C39B076123047@CGEXC03.compugraf.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <3FFA1818C1550246933DEA311C39B076123047@CGEXC03.compugraf.com.br>
User-Agent: Mutt/1.5.9i
Content-Transfer-Encoding: quoted-printable

On Thu, Aug 24, 2006 at 05:27:58PM -0300, Andr=E9 Jos=E9 Guergolet wrote:
> Hello all,  I'm using the Postgres 8.0 and my product creates 7
> connections at the server.
> =20
> One of my connections do an update at a simple table with 360 rows
> and I've got many table locks. How I can take more scability?

It's pretty hard to tell, given what you're telling us.  The UPDATE
will take a write-blocking lock on each of the rows for the duration
of the transaction.  You shouldn't have any table locks, unless
you're not telling us something.  You should post more detail.  Why
do you think you have table locks, to begin with?

A

--=20
Andrew Sullivan  | ajs@crankycanuck.ca
The plural of anecdote is not data.
		--Roger Brinner