Re: One long transaction or multiple short transactions?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
Cc: "Graeme B(dot) Bell" <graeme(dot)bell(at)nibio(dot)no>, Laurent Martelli <laurent(dot)martelli(at)enercoop(dot)org>, "pgsql-performance(at)postgresql(dot)org list" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: One long transaction or multiple short transactions?
Date: 2015-10-17 17:13:38
Message-ID: 20151017171338.GB28038@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 2015-10-17 10:26:01 -0500, Jim Nasby wrote:
> Except inserts *do* take a lot of locks, just not user-level locks.
> Operations like finding a page to insert into, seeing if that page is in
> shared buffers, loading the page into shared buffers, modifying a shared
> buffer, getting the relation extension lock if you need to add a new page.
> Then there's a whole pile of additional locking you could be looking at for
> inserting into any indexes.
>
> Now, most of the locks I described up there are transaction-aware

Missing *not*?

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jim Nasby 2015-10-17 20:43:29 Re: One long transaction or multiple short transactions?
Previous Message Jim Nasby 2015-10-17 15:26:01 Re: One long transaction or multiple short transactions?