pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: Lock Problem
Date: Thu, 24 Aug 2006 16:52:55 -0400
Message-ID: <20060824205255.GA24499@phlogiston.dyndns.org> (raw)
In-Reply-To: <3FFA1818C1550246933DEA311C39B076123047@CGEXC03.compugraf.com.br>
References: <3FFA1818C1550246933DEA311C39B076123047@CGEXC03.compugraf.com.br>

On Thu, Aug 24, 2006 at 05:27:58PM -0300, André José Guergolet wrote:
> Hello all,  I'm using the Postgres 8.0 and my product creates 7
> connections at the server.
>  
> 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

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

view thread (2+ messages)

Message-ID: <20060824205255.GA24499@phlogiston.dyndns.org>
Permalink:  ../20060824205255.GA24499@phlogiston.dyndns.org/
Also on:    postgresql.org/message-id/20060824205255.GA24499@phlogiston.dyndns.org

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: ajs@crankycanuck.ca
  Subject: Re: Lock Problem
  In-Reply-To: <20060824205255.GA24499@phlogiston.dyndns.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox