pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Markus Schiltknecht <markus@bluegap.ch>
To: Joost Kraaijeveld <J.Kraaijeveld@Askesis.nl>
Cc: pgsql-general@postgresql.org
Subject: Re: Locking in PostgreSQL?
Date: Wed, 06 Dec 2006 08:11:44 +0100
Message-ID: <45766D30.3010008@bluegap.ch> (raw)
In-Reply-To: <1165388652.6396.1.camel@panoramix>
References: <1165388652.6396.1.camel@panoramix>

Hi,

Joost Kraaijeveld wrote:
> Does PostgreSQL lock the entire row in a table if I update only 1
> column?

Yes. In PostgreSQL, an update is much like a delete + insert. A 
concurrent transaction will still see the old row. Thus the lock only 
prevents other writing transactions, not readers.

Regards

Markus

P.S.: please do not cross post such questions.



view thread (10+ messages)  latest in thread

Message-ID: <45766D30.3010008@bluegap.ch>
Permalink:  ../45766D30.3010008@bluegap.ch/
Also on:    postgresql.org/message-id/45766D30.3010008@bluegap.ch

 · 

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-performance@postgresql.org
  Cc: markus@bluegap.ch, J.Kraaijeveld@Askesis.nl, pgsql-general@postgresql.org
  Subject: Re: Locking in PostgreSQL?
  In-Reply-To: <45766D30.3010008@bluegap.ch>

* 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