Date: Sat, 17 Oct 2015 19:13:38 +0200
From: Andres Freund <andres@anarazel.de>
To: Jim Nasby <Jim.Nasby@BlueTreble.com>
Cc: "Graeme B. Bell" <graeme.bell@nibio.no>,
 Laurent Martelli <laurent.martelli@enercoop.org>,
 "pgsql-performance@postgresql.org list" <pgsql-performance@postgresql.org>
Subject: Re: One long transaction or multiple short transactions?
Message-ID: <20151017171338.GB28038@awork2.anarazel.de>
References: <002a01d0ffe4$2c630e60$85292b20$@stonebanks.ca>
 <003d01d0ffe4$9ae8f890$d0bae9b0$@stonebanks.ca>
 <A76B25F2823E954C9E45E32FA49D70ECCD54DF53@mail.corp.perceptron.com>
 <00fe01d10159$8e731980$ab594c80$@stonebanks.ca>
 <56176288.9040500@enercoop.org>
 <884892BF-DD42-4E0A-8973-3A691E25E450@skogoglandskap.no>
 <56226889.4050609@BlueTreble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <56226889.4050609@BlueTreble.com>
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

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*?


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance