Re: AccessExclusiveLock on tuple?

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bill Moran <wmoran(at)potentialtech(dot)com>, pgsql-general list <pgsql-general(at)postgresql(dot)org>
Subject: Re: AccessExclusiveLock on tuple?
Date: 2015-12-02 18:47:52
Message-ID: 81522478-1A6A-4B1C-A9F5-5FCDD70D4F8A@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Dec 2, 2015, at 10:29 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The short answer is that heavyweight tuple locks can be taken internally
> by UPDATE, DELETE, and other row-level operations, and the specifics of
> which type of lock any given action takes are implementation details that
> can change from time to time.

Great, thank you!

--
-- Christophe Pettus
xof(at)thebuild(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Steele 2015-12-02 19:56:53 Re: Pgbasebackup help
Previous Message Tom Lane 2015-12-02 18:29:16 Re: AccessExclusiveLock on tuple?