pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Jim Nasby <Jim.Nasby@BlueTreble.com>
Cc: Graeme B. Bell <graeme.bell@nibio.no>
Cc: Laurent Martelli <laurent.martelli@enercoop.org>
Cc: pgsql-performance@postgresql.org list <pgsql-performance@postgresql.org>
Subject: Re: One long transaction or multiple short transactions?
Date: Sat, 17 Oct 2015 19:13:38 +0200
Message-ID: <20151017171338.GB28038@awork2.anarazel.de> (raw)
In-Reply-To: <56226889.4050609@BlueTreble.com>
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>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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*?


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



view thread (13+ messages)  latest in thread

Message-ID: <20151017171338.GB28038@awork2.anarazel.de>
Permalink:  ../20151017171338.GB28038@awork2.anarazel.de/
Also on:    postgresql.org/message-id/20151017171338.GB28038@awork2.anarazel.de

 · 

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: andres@anarazel.de, Jim.Nasby@BlueTreble.com, graeme.bell@nibio.no, laurent.martelli@enercoop.org
  Subject: Re: One long transaction or multiple short transactions?
  In-Reply-To: <20151017171338.GB28038@awork2.anarazel.de>

* 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